> switches off animation at the risk of seeming to flog the proverbial dead horse...
Consider the <<option chkAnimate>> setting. Suppose I have a Windows system with both IE and Firefox. Let's also suppose that IE is slow, and doesn't always display the animations smoothly and can even make the document nearly unusable in some situations. Turning off chkAnimate for IE helps alot. However... I normally use Firefox rather than IE, and Firefox is much faster, so I don't want to turn off the animation effects there. I want different values for the same setting, based on which browser I am using. Similarly, consider chkBackupFolder. Suppose I view the same document on two systems, one at work, and the other at home. Both use the same software (OS, browser, etc.). However, when I'm at work, the TW document is on a shared network server, but when I'm home, it's just in a local folder (or even kept on the thumb drive). Different systems = different directory structures = different value for chkBackupFolder. Thus, the desired values for chkAnimate and chkBackupFolder depends upon the *environment* in which I am currently operating, rather than being specific to a given user or document. In contrast, consider the chkIncrementalSearch option. This is more of a *user-specific* setting. If I prefer to disable incremental searching, I'd like that behavior to be applied, regardless of the platform I am currently using, to every TW document I view... even if that document was written by someone else and then published online for read-only viewing. Of course, there are also options, such as chkHttpReadOnly, that clearly are intended be *document-specific*. For example, the author of a document may want to be able to edit the document when posted online, so they "hard-code" config.options.chkHttpReadOnly=true; into a [[ConfigTweaks]] (or [[CookieJar]]) tiddler, tagged with 'systemConfig'. This setting is then applied whenever that document is loaded, regardless of where it is viewed or who is viewing it. Thus, there are really three different types of settings: * environmental * user-specific * document-specific Environmental settings can use browser-cookies. Document-specific settings can use a hand-written [[ConfigTweaks]] tiddler or a [[CookieJar]] tiddler generated by CookieSaverPlugin. The "missing link" is support for *user-specific* settings. Perhaps something like the external "prefs.js" file used by FireFox would fit the bill. The file would have to be portable and cross- browser compatible, and could probably be auto-generated by TW in response to a click on a command link (or whenever the current document is saved). thoughts? -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 -~----------~----~----~----~------~----~------~--~---
