> I'm sure it's wonderful but lets make it so TW users don't have to deal with > this complicated stuff just to have a sane way to turn on backups or > autosave.
Install CookieSaverPlugin means that you don't have to deal with *any* complicated stuff if you don't want to. The CookieJar contents are maintained automatically, so the users *never* need to know how it works... that's the one of the main feature points of the plugin... providing in-document persistent settings *without* requiring people to hand-edit a configuration tiddler (or even know *how* to edit it!). When an <<option chk...>> or <<option txt...>> input is changed, there's *no* additional actions that the user needs to do... the CookieJar is automatically updated behind the scenes. You could even tag the CookieJar with 'excludeLists' so it was hidden from the sidebar tabs and then the user wouldn't even know that such a tiddler exists. As far as they are concerned, the only difference is that they changed a setting in the normal way and it was remembered in the document... nothing else is required of them, except for the unavoidable need to save the file at the end of the session to preserve the changed settings (if 'autosave' isn't enabled, of course). -e --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
