I'm using tiddlywiki's browser-independent file interface to load/save files for a javascript application I'm writing (and will soon share to the tiddlywiki list). Overall I've found it very easy and useful. There's one small rought spot, however. I use tiddlywiki's getLocalPath method (from Saving.js) to generate an appropriate filename. While getLocalPath seems very generic and useful, it is entangled in the broader tiddlywiki codebase in two ways. First, it is in Saving.js which is devoted to thinking about tiddlers and the tiddlywiki-specific file format. Second, its first line makes a reference to config.options, which is part of the Config.js file, which is full of lots of tiddlywiki-specific stuff. As a result, I choose to copy getLocalPath our of Saving.js and modify the first line to omit needing to load all of Saving.js and config.js and whatever they depend on.
Given that pathname computation seems a highly useful and general mechanism that is relevant to saving any file, not just tiddlywikis, it would seem natural to me to make some version of getLocalPath a part of your lower-level file load/save mechanism, which seems lately to be migrating into http://svn.tiddlywiki.org/Trunk/core/jquery/plugins/jQuery.twFile.js . Thanks for reading. I'd certainly welcome any feedback, but won't be upset if I don't get any. -David Karger --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
