Assuming that:* you //are// online when you need to edit your TWD* you (can) trust the server with your content- if not, read on...how about a dedicated web service for editing your (locally kept) documents.You would go to, say, edit.tiddlywiki.com, upload your document and start editing. When you're done, you'd click the download button and get it back.If you needed to collaborative editing, you could have a temporary URL assigned for the document, that you could share.If you reject either of the preconditions, you'd of course have to install the (open-source) server on your own PC. Extra advantages: All the services (like wysiwyg editor, auto-save, etc.) that a server could offer.The Google App Engine/SDK would be a perfect basis for a platform-neutral implementation.Heck, the service could even be ad-sponsored. :-) Poul On 12 Nov., 11:44, Jeremy Ruston <[email protected]> wrote: > I've been doing some experiments to explore how TiddlyWiki might be > able to use standards-compliant browser techniques to accomplish file > saving. > > The motivation is that we're already seeing browsers (finally) > tightening up some of the security loopholes that have historically > allowed TiddlyWiki to function. Establishing a standards-compliant way > of operating, even if it's a bit clunky, would go a long way to give > us all confidence that TiddlyWiki can continue to function properly in > the long term.
-- 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.
