That's great! > Which options do you think should be persistent, and which options > should be in cookies?
This depends on the use of TW. If it's a document "for myself", most of things should be backed, including authorName, autoSave, RegExpSearch, probably sliders' states. AutoSave is most important since some browsers (including Opera) don't notify when you close a tw- document without saving. On the other hand, if TW is used as a site (or part of a site) most of them should be cookie-based because they are for users. > Which should take precedence a persistent option or a cookie? That > is should a persistent option overwrite an option previously set in a > cookie, or should the cookie value take precedence? I think this worths adding one more option. If you do so, when TW is used just by the author, it should be set so that backed ones are precedence. For use as a site, it's just switching that option that's enough to work it properly. Now, let's consider a situation if a tw-document is used by a team of editors. This goes more complicated. I think each author should have some structure describing his or her preferences, like a author_name_SystemSettings tiddler (and perhaphs group_name_SystemSettings). The thing is, TW should somehow recognize the author. This can be done either manually (by some sort of authentication) or automatically (based on cookies, I guess). As for now, I don't see any beatiful solution.. On 18 ноя, 16:06, Martin Budden <mjbud...@gmail.com> wrote: > I'm pleased to announce the TiddlyWiki 2.6.2 beta release. > > This release consists of a number of minor usability and hackability > enhancements, as described athttp://trac.tiddlywiki.org/wiki/History, > and one fairly major enhancement. > > The major enhancement is the addition of persistent options, also > known as 'baked cookies'. This is the ability of TiddlyWiki to store > some of its options in a tiddler, the SystemSettings tiddler, so that > these options are retained even if the user deletes all their cookies, > or moves the TiddlyWiki to another computer. > > The persistent options are more fully described at: > > http://tiddlywiki.com/beta/#PersistentOptions > > We are soliciting feedback about Persistent Options as part of this > beta release, in particular: > > 1) Which options do you think should be persistent, and which options > should be in cookies? > > 2) Do you think the persistent options have been explained properly, > and do you have any suggestions to improve the explanation? > > 3) Which should take precedence a persistent option or a cookie? That > is should a persistent option overwrite an option previously set in a > cookie, or should the cookie value take precedence? This has been the > subject of some discussion, and we are by no means sure which is the > better option. In the beta the persistent option overwrites the cookie > option. > > Note that for a standalone TiddlyWiki, the impact of the difference in > precedence is not that great, but for TiddlySpace the impact is more > significant: it means an option set locally by a user in a cookie can > be overwritten by another user of the TiddlySpace, if that option is > persistent. > > Martin -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
