That's correct, unless the TiddlySaver.jar file is found in the same
folder as the TiddlyWiki HTML file.
> 1. Is this an accurate assessment as to the current state of the
> discussion? and
YES
> 2. Is something really being done about that eliminate-the-cookies
> discussion? Or is it going to be on a perpetual backburner like the
> plugin repository?
I'm just about to post a patch for consideration. It eliminates the
need for cookies entirely.
> I for one want to register my desire to see TiddlyWiki get to the
> point where it works on IE, Firefox and Chrome (not to mention other
> browsers) without new users having to download applets or tweaking
> their command lines, whatever those are. I know many people that
> either wouldn't take the time to do something like that, or that would
> refuse to do so because they don't know much about such things (I
> don't either) and they fear that doing either of those things would
> expose them to security risks.
I can't see a route for Chrome to be able to save changes from a
standalone TiddlyWiki without using TiddlySaver. jar.
It's not as bad a user experience as you might think; tw.com now
automatically offers a ZIP file that contains the empty.html file
along with TiddlySaver.jar. Users generally don't need to do anything
special.
But as I say, it behaves like this not because I want it to, but
because we can't see a better way to implement saving on Chrome.
Best wishes
Jeremy
> Most of my efforts with TiddlyWiki in the past have been in the area
> of making TW user-friendly for new people. My new No-Brainer Notes
> adaptation is another, more recent foray into the same territory. But
> I don't want to make NBN accessible from my website and talk about how
> easy TW is to use if in reality just to use TW you have to take a
> crash course in enabling Javascript and configuring browsers for
> cookies.
>
> I would love to hear your comments in this regard.
>
> Dave
>
> >
>
--
Jeremy Ruston
mailto:jer...@osmosoft.com
http://www.tiddlywiki.com
Cheers
Jeremy
Yup, that's right.
I did some experiments on embedding tiddlysaver.jar into the tw.html
file itself; you still need to right-click and save-as to get it on
the disk, but it means that at least everything can be crammed into a
single package:
http://autotiddlysaver.tiddlyspot.com/
Best wishes
Jeremy
Whoa, careful there!
While it's true that the plugin library is taking longer than
anticipated (for the record, that's because it turns out to be a really
complex system), that work has been out in the open, visible to anyone
following the Trac timeline (commit history), my Twitter stream, IRC
conversations or the occasional note in postings here on the TW groups.
In fact, you could take the bits in Subversion now to aggregate and
browse plugins from a large number of repositories. It's just not ready
yet to be used by the general population (I expect there to be an alpha
release soon though).
Of course anyone is more than welcome to contribute code in order to
speed up the progress.
Having said that, I could certainly do a better job of communicating the
progress on this project - but I don't like writing fuzzy posts, so I
generally choose to do actual coding instead.
[/OT]
-- F.