On Fri, 11 Jan 2013, Clifford Bressette wrote:
I will use these three engines to extract individual tiddlers from TW files and store them as individual UTF-8 files which can be used to easily export tiddlers based on tags and render new contextual TW files. I will also use these engines to allow a user to create, modify and delete groups of tiddlers.
It seems like much of the functionality that you are after is already available in several of the server side engines that exist, notably TiddlyWeb (the one that I wrote, find more about it at http://tiddlyweb.com/ ). Where the difference comes in is that the functionality has been assembled to provide for the delivery of tiddlers (in various forms) through a web server, rather than directly at the filesystem level as you desire them. This suggests a couple of strategies that would be less labor intensive than your plans: * Modify a server side (like tiddlyweb) to remove the web server component: let it operate as the kernel of a gui you create. * Accept the concept of a distributed architecture, but run it locally. However, I recognize that ignores one of your main goals: "to have one .c file which adheres to ANSI C standards and as such can be compiled on almost any computer". That's an impressive goal but the thing you are interested in creating is a huge undertaking. You're effectively planning to reimplement a gui web browser (firefox, chrome/webkit, etc). Since most web browsers these days are open source, have you considered forking them to get at the core presentational and javascript functionality they provide, and then adding in your own support for tiddlers-on-disk? -- Chris Dent http://burningchrome.com/ [...] -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev?hl=en.
