That's just too damn cool. And if wasn't such obvious a path to use node.js (or any js runtime/server) with tiddlywiki, the synchronicity would be scary.
I've been mulling over (for a couple of months) the idea of using node.js to implement a store-and-forward message queue to use with TW, for many of the same reasons you selected it, I'm sure. Mainly I wanted to be able to use the same code/modules in the node.js server as I would in the tiddlywiki plugin that would send/receive the messages. node.js runs on the 2 main O/Ses I care about (Linux and XP), and javascript is now an integral part of the Gnome desktop. That makes a pretty level playing field for better integration of TW based apps with my personal desktop, and still provding for a relatively simple connection path from my desktop/TW (F15/Gnome) talk to my laptop/TW (XP). My initial goal for a node.js mq process is for a tiddlysnip alternative, that can run outside the browser, and is platform agnostic - as far as node.js is, at least. I watched the discussion over formalizing standard tiddler fields and content with hope and fear... hope that it would lead to interesting new developments, and fear that the core tiddler might get bogged down with too much baggage (the latter was a pretty remote possibility, I know, if you project forward based on TW history so far). I'm glad the status quo appears to be unchanged, leaving the core tiddler untouched, and letting (requiring?) anyone implementing sync or external stores to add on their own metadata to facilitate passing tiddlers back and forth. I think that's one of the major strengths TW has - it's extremely open. and simple, at it's core. Only the thing that must exist to make the core work, are in the core. Anyway, I'm really excited to hear about the progress you've made - and I can tell you're pretty excited about it too - I totally get it. Hopefully, I can find/make some time to actually put some code together for my node-mq project... so far, I've only had time to research existing modules that I might be able to press into service, that work under node.js AND brower runtimes (I figure if both those work - integrating to the desktop - directly via desktop extension, or via standalone applet - should be a snap). The structured format for the intermediate tiddler state (parsed, but not yet rendered) would likely make tiddler exchange (peer-2-peer, client/server, etc) simpler and more portable. This is a more momentous anncounment - to me anyway - than when you made the *first* TW5 available for preview. I can't wait to see what's next! Sounds like it's time for me to sub to the TWDev group... even if it's just to listen in. Kudos all around. -- Jim -- 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.
