persistent options (without cookies)

[FND]

As discussed  here and  here, TiddlyWiki should have a mechanism to "bake" options into the document (instead of or in addition to using cookies).

[FND]

[comment originally posted by EricShulman?]

see  http://www.TiddlyTools.com/#CookieSaverPlugin for a solution...

The plugin basically hijacks the saveOptionCookie() function so that, in addition to the normal cookie saving behavior, the cookies are automatically written into a tiddler called CookieJar?? as lines of javascript, e.g.:

config.options.chkSomething=true;
config.options.txtWhatever="this is text";
etc.

The CookieJar?? is tagged with systemConfig, so that these settings are automatically applied each time the document is reloaded, effectively providing what I have called "portable cookies" (because they travel with your document, instead of being associated with your browser).

The StorySaverPlugin?? includes support for multiple sets of portable cookies, each associated with a different username so that, when a document containing a CookieJar?? tiddler is shared, MY saved portable cookies will not be applied to THEIR viewing experience.

The plugin also features a customizable "allowCookies()" test function, that provides some control over cookie data privacy by allowing you to block certain cookies from ever being written into the CookieJar?? although they are still being securely stored as "real" cookies in your browser.

[FND]

Baked Options Patch by JeremyRuston?

[FND]

Second pass at a patch by JeremyRuston?

[FND]

Revised patch that packs all the options into a single cookie by JeremyRuston?

[FND]

[comments originally posted by JeremyRuston?]

I've uploaded a patch for comment. It's similar to Eric's plugin, but doesn't use a systemConfig tiddler, instead it introduces a new SystemSettings?? shadow tiddler. This is because in some server side environments it will be undesirable to require users to have the permissions to modify a systemConfig tiddler just to make a setting persistent.

I've added a revised patch that now also deletes cookies when they are reset to their default values (see ticket #757). There's some more refactoring and bugfixes too

[FND]

As an alternative to baking options into the document,  DOM Storage might be used for user-specific preferences in modern browsers.

[FND]

This should be revisited via a discussion on the groups. The current patches introduce new concepts - perhaps it would be preferable to go with Eric's approach.

[MartinBudden]

Milestone 2.6.2 deleted