Thanks for all the comments everybody. I'm just working my way through
them and will post replies later today.
Martin
On Nov 20, 3:19 pm, whatever kbrezov...@gmail.com wrote:
Well, as long as it's not a bug. Though, as far as I know we're still
in November, not in December. :D
w
On Nov 20,
We'll certainly give consideration to the suggestion of using the
filename as part of the cookie id, but not as part of the 2.6.2
release - it's too large a piece of work to slip in at the end of the
release cycle.
However, the baked cookies do offer a solution to your problem - the
UserName has
Ton,
the reason for the current syntax is that it is conceivable that
someone might want to use the value cookie as an option. (Here's a
stupid example: someone might have the nickname cookie, which they
might want to set as their username.) I know this is somewhat
contrived, but there is also
Hi!
I was just checking out the beta and I noticed that dates seem to be
all out of whack. For example, http://tiddlywiki.com/beta/#PersistentOptions
shows date modified 20 December 2010 and http://tiddlywiki.com/beta/#HelloThere
shows date modified 15 December 2008 (possible, but unlikely,
Hi!
Also, considering that TW already has a backstage mechanism for
setting options (Tweak and/or Options from AdvancedOptionsPlugin (1)),
it would be nice if such a mechanism were enabled for SystemSettings.
It could be added as a tab to existing options, where you could add a
tick to make it
Also, considering that TW already has a backstage mechanism for
setting options (Tweak and/or Options from AdvancedOptionsPlugin (1)),
it would be nice if such a mechanism were enabled for SystemSettings.
It could be added as a tab to existing options, where you could add a
tick to make it
Well, as long as it's not a bug. Though, as far as I know we're still
in November, not in December. :D
w
On Nov 20, 3:40 pm, Jeremy Ruston jeremy.rus...@gmail.com wrote:
Also, considering that TW already has a backstage mechanism for
setting options (Tweak and/or Options from
This is a very nice enhancement indeed.
The syntax however is i.m.h.o. somewhat confusing. Why append the
option-name with _cookie:?
a) to me it looks like an unnecessary complication of the syntax.
b) the syntax more or less suggests (because of the closing colon)
that you could still provide a
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
My suggestion would be that as part of the implementation of
persistent (Baked) cookies, consideration be given to including the
current file name as part of the cookie ids. I realize not everyone
uses multiple open TW files at the same time, but the many uses of
cookies in TW currently means
I agree with Alan on using filename as part of the cookie name or
perhaps a random ID. Recently, I had four different TWs open, and the
username was same in all of them, even though it wasn't supposed to
be.
As for which should take precedence, I think the cookies. I mean, you
set some default
11 matches
Mail list logo
