As you might know, the Google Chrome browser does not store cookies for
local files - which means TiddlyWiki user options cannot be saved.*
The developers have decided not to fix this issue, for now:
> marking as WontFix. People can still comment on the bug if they feel
> it's important, and we can always revisit later on.
So you might want to alert them that this is not an insignificant issue:
http://code.google.com/p/chromium/issues/detail?id=535
(All you need is a Google account, which you probably already have for
posting on the TiddlyWiki groups.)
-- F.
Another approach which perhaps can be made to work now quickly for
GoogleChome woudl be to use the Flashplayers' own cookie system.
Some people love to hate Flash, but I believe it has a *lot* to offer TW
and vice versa [audio video cookies javascript flex air etcetc].
Adobe AIR for example should make it very easy to have TW truly running
as a standalone desktop web app, since AIR speaks javascript
actionscript and HTML.
Flash Cookies are known as 'local shared objects' LSO - similar to HTTP
cookies, but the default storage size is 100Kb :-)
JSON formatted data should work fine to smooth the transmission between
TiddlyWiki and Flash
some reading..
What are local shared objects?
http://www.adobe.com/products/flashplayer/articles/lso/
What are third-party local shared objects?
http://www.adobe.com/products/flashplayer/articles/thirdpartylso/
HOWTO: SharedObjects for Local Storage AS3
Shared Object Reader [in python and php]
http://www.sephiroth.it/python/solreader.php
http://drawlogic.com/2008/01/10/howto-sharedobjects-for-local-storage-as3/
Flash with Flex
http://marxsoftware.blogspot.com/2008/05/flash-cookies-with-flex.html
HOWTO: SharedObjects for Local Storage AS3
January 10, 2008 — drawk
Using SharedObjects in Flash is very simple. Flash has SharedObjects
that have been in the player since Flash6 when the introduction of Flash
Communication Server which is now Flash Media Server which is releasing
version 3 soon (also remote SharedObjects in Red5
<http://osflash.org/red5> is an open source RTMP media server that is
based on Flash Media Server). So we can thank this release for
SharedObjects, Camera objects, Audio, lots of the NetConnections,
protocol enhancements and many other things. However to keep the tips
simple we will just touch on the local usage and post a series of posts
on these objects.
http://drawlogic.com/2008/01/10/howto-sharedobjects-for-local-storage-as3/
------
Jason
While I generally wouldn't mind that, there are two different types of
settings: document configuration and user preferences (think authors vs.
readers).
I'd love to have an alternative to manually putting code into a
ConfigTweaks tiddler - but I how could we allow different users to have
different settings (e.g. username, animations) if not with cookies?
Either way, we should have this discussion on [twdev].
-- F.
I don't think we should be campaigning to make Chrome do cookies for local files. I think rather it's time we make TiddlyWiki stop using cookies for TW settings.
While I generally wouldn't mind that, there are two different types of
> it's time we make TiddlyWiki stop using cookies for TW settings.
settings: document configuration and user preferences (think authors vs.
readers).
I'd love to have an alternative to manually putting code into a
ConfigTweaks tiddler - but I how could we allow different users to have
different settings (e.g. username, animations) if not with cookies?
See
> A kind of ini tiddler that fixes default options in the TiddlyWiki but that
> can to be set and changed easily with a macro like <<option>> should be
http://www.TiddlyTools.com/#CookieManagerPlugin
The <<cookieManager>> interface includes a "bake cookies" button to...
LOL. That's awesome. :-)
--
Scott Elcomb
http://www.psema4.com/
http://www.psema4.com/blog/
http://www.google.com/reader/shared/14892828400785741937
I know - however, experience shows that not all users are comfortable
setting startup flags like that.
Either way, we're currently looking into options to rid TiddlyWiki of
these cookie issues altogether.
-- F.
Modify the target location of your Google Chrome shortcut, e.g.
"C:\Programs\Google Chrome\chrome.exe" --enable-file-cookies
(It's been a while since I've done this on Windows, so the placement of
the quotation marks might be off.)
-- F.
PS: q.e.d. ;)