On Fri, Feb 19, 2010 at 8:39 AM, Jeremy Ruston <[email protected]> wrote: >> How does TiddlyWiki5 support newer browsers which don't allow local >> documents writing to the filesystem? > > As with the classic TiddlyWiki, it will be possible for a plugin to > override the file saving code so as to target some other way of > persisting content.
I'm hoping that "following the microkernel approach" means it will be possible to cook a TiddlyWiki which doesn't include the local filesystem saving, rather than having to add code to 'override' redundant core code, as at present. > Generally, all these technologies take the form of a client-side > accessible data cache. My conceptual problem with using them for > tiddler storage is that the modified tiddlers end up being stored in a > somewhat ephemeral way, living in the browser, and the user loses the > usual TiddlyWiki comfort of being able to reach out and inspect their > data at any time. However, there are clearly some interesting > situations (like Safari on the iPhone) where these are the only > available techniques for persistent storage. That's true, but that might change, and Eric's point that we should embrace HTML 5 techniques as they become available is a good one. For example the W3C File API currently has no provision to save files locally, but may be extended to in the future. -- Paul (psd) http://blog.whatfettle.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.
