Well, TiddlyFox seemed the right candidate when thinking of local file io, at least I didn't quite see (better) alternatives atm. But I can see that such requirements not only involve sensitive matters (browser security) but also significant efforts for architectural specification, let alone implementation, testing, and adaptation within TWx plugins.
It's just that I think that a well defined local and / or remote file-io API opens up vast potentials for dynamic aggregation, construction, analysis, management of tidbits that are somewhat outside the scope of being managed in TW itself (big binaries), but within the scope of the type of applications or knowledge-bits that users want to keep track of using TiddlyWiki. So, "How do I get this or that into TiddlyWiki?" seems a question often asked. For example, I can imagine TiddlyWiki as a front-end for code documentation whereas some plugin inside TW would crawl a source folder and extract the documentation bits into a tiddler-representation. For example, the TW5 codebase could have all the desired code documentation in a well defined format preceding an object or function declaration which would then be put together in a TiddlyWiki for documentation purposes in terms of an API. Sure, this can be done with some kind of node.js implementation... but if it could be done with nothing but a browser that would be quite something. Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/groups/opt_out.
