I know you have write it because i try to reverse it in the "couch concept" The big difference between tiddlyweb (that i use also) and couch is the notion of recipe and bag, and the fact that tiddlyweb build automatically all list needed by the framework. This is not true in couch and we need to build every view & list to match the two concept
So to port TW on couch, we have 2 solutions ,the port the tiddlyweb concept on another db backend like it was done with mysql for Tspace (i think), or the build of a new TW adaptator who's more couch specific And i think the second one is my first path Another thing is to know if we do the port " a la couchapp" (splitting of the code & more elegant in the couch world) or "a la TW" everything in one file and the data outside (more compatibility with future TW development) So for the moment that's more try and error (with many error) Ph Koenig Aka Unclephil On Sep 6, 8:02 pm, FND <[email protected]> wrote: > > For the future, i'm busy to split the TW file structure in the > > couchapp one, and then i'll try to fine tune the result during my > > freetime [...] So be patient ... or faster than me > > Actually, why don't we combine our efforts? I don't have a whole lot of > experience with CouchDB, but wanted to get back to playing with it > anyway - and having worked on the TiddlyWiki<->TiddlyWeb side of things > a lot, I could probably help move things along. > > If you could provide some guidance on design documents, views and such, > I could quickly come up with some exemplary code to store and retrieve > tiddlers (preferably over on [twdev] to keep the noise down). > > -- F. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
