> I know you have write it because i try to reverse it in the "couch > concept" [...] tiddlyweb (that i use also)
Oh, good to know. > 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 I agree an adaptor is the right approach, as TiddlyWiki is perfectly capable of interacting with CouchDB by itself. We can worry about compatibility with TiddlyWeb's HTTP API (or a subset thereof) later. (TiddlyWeb's MySQL store is just an extension of the server-side's storage layer, with no impact on the HTTP API. I had experimented with such a store implementation using CouchDB a while back*.) > 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 The way TiddlyWebWiky handles this is to store each tiddler individually and populating an empty TiddlyWiki template by adding the appropriate HTML representation for each tiddler to the HTML document (above the "<!--POST-STOREAREA-->" marker present in each TiddlyWiki). I'm not sure which facilities CouchDB offers for such server-side processing though. -- F. * http://gist.github.com/310251 -- 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.
