gr2m

9 ms·

31.
by gr2m 14y ago
Lazare, this is awesome, thanks so much! Let us know if you'd like to look closer into Hoodie, happy to assist
32.
by gr2m 14y ago
Key difference: kan.so is Couch specific. Hoodie is not. We do not try to make another nice library to wrap CouchDB. We try to make a nice JavaScript API for the most common backend tasks. We start with a dream API, and build from there.
33.
by gr2m 14y ago
so sorry that we didn't get to it yet. Hoodie is certainly not OS X exclusive, we just have some DNS magic that helps developing locally, that's Mac only at the moment. Hoodie is just Node.js & CouchDB, you should be able to run it with
34.
by gr2m 14y ago
hood.ie has a different approach. Meteor brings backend logic to the frontend. hood.ie tries to hide the backend entirely and provide an API that feels natural for the frontend environment. The JavaScript API is what we care about most. We
35.
by gr2m 14y ago
<3
36.
by gr2m 14y ago
we currently use localStorage. But we <3 PouchDB, just didn't get to it yet. Shouldn't be hard to change that, or to build your own store wrapper providing the same API
37.
by gr2m 14y ago
backbone
38.
by gr2m 14y ago
I've made a backbone adapter a while a go: https://github.com/hoodiehq/hoodie.js/blob/master/stuff/back... shouldn't be hard to make one for Angular. Happy to help
39.
by gr2m 14y ago
permissions is handled directly by CouchDB. Every user has an own database that only he/she has access to. Synchronization between accounts can be done via shares. We don't have validation at the moment. You can store whatever you like, it'
40.
by gr2m 14y ago
are you on Windows or Linux? Would be great if you could help us to migrate it. hoodie is basically CouchDB + node.js, nothing fancy. We just do local DNS magic, creating *.dev domains like http://pow.cx/ , that is only compatible with Mac
41.
by gr2m 14y ago
at first, Hoodie is just a Store for data. So instead of Backbone, Angular etc storing their data via AJAX on a server, or in LocalStorage, we can very simply build adapters for all of the MV* frameworks to use Hoodie as their store. This w
42.
by gr2m 14y ago
tay, I'm one of the developers behind hoodie. I agree that there is no silver bullet for apps, and Hoodie does not try to be one. Our main goal is to enable as many people as possible to build real, data driven apps. Think of it this way: i
43.
by gr2m 14y ago
The problem was related to attachements, I think in your particular case it was an image in your email signature.
44.
by gr2m 14y ago
Thanks for the nice feedback & your suggestions, so encouraging! > Can you please enable a couple of sub-task level to make it really useful, similar to Google Task? We do not plan to add sub tasks at the moment. In general, we do n
45.
by gr2m 14y ago
wow, thanks so much for the nice feedback! We really appreciate it!
46.
by gr2m 14y ago
Problem resolved, thanks for the support!
47.
by gr2m 14y ago
Yeah, sorry for that, Thomas! Just for your information: The problem is not that you've sent the email to yourself, it's something else. I'll keep you posted.
48.
by gr2m 14y ago
We're here to stay ;-) Would you mind to share the other services that come to your mind but didn't make it in the long run? I'd be very interested, because I don't know any
49.
by gr2m 14y ago
Oh nice, I didn't know about Sandy yet! But I thing it goes in a different direction: Sandy tried to be your personal assistant if I get it right, we rather try to help you and your collaborators to keep the oversight of tasks when email is
50.
by gr2m 14y ago
Hey Joshka, thanks for the feedback! > Have you considered another email address rather than mail@task.li perhaps task@task.li so it's really easy to autofill That's actually a great idea. I've just added task@task.li next to mail@task.
51.
by gr2m 14y ago
ooops, good catch ;-) We just fixed it, thanks for bringing it up!
52.
by gr2m 15y ago
amen.
53.
by gr2m 15y ago
that's because there is no _changes feed in the current couchbase 2.0 server.
54.
by gr2m 15y ago
The features I got exited most about (and am relying on today) are: databases per user, continuous replication and the _changes. From my understanding, these are not part of the CouchBase server, right? What are the future plans for these