#Tiddlydesktop opening install#
#Tiddlydesktop opening full#
#Tiddlydesktop opening download#

#Tiddlydesktop opening download#

If you're currently viewing this page on the web, you should download a copy now by clicking the save icon at the end of this paragraph: If you don't create a copy, you won't be able to keep track of which exercises you've completed, review takeaways, create bookmarks, or save your place when you stop reading.

#Tiddlydesktop opening full#

To get the full value out of GTW, you'll want to create your own copy of this wiki this will allow GTW to save information about your progress and personalize the book for you.

And if I have to, I'll have even more reason to want to ditch recent builds of these browsers that seem to be forgetting or missing the point entirely.Grok TiddlyWiki is a TiddlyWiki itself, as you may have noticed or suspected by now. I really don't want to have to go installing an old version of Firefox, or worse, whipping up a VM from an old, insecure version of Ubuntu or Vector Linux. In the past couple weeks, it looks like whatever tolerance Firefox was showing for known files that I had self-edited has completely dried up, and the files I prefer to use most are now 'stuck' in their last state. I don't want to have to 'pop a pill' to 'abate the symptom' (possibly causing some other symptom later).

But then I'm sure there are other similar projects that are now rendered valueless without the ability to save. I figure there's some way of hacking the Tiddlywiki extension to also supply the save ability again to WikiOnAStick files too. But, I'm not interested in having another browser window open all the time, and last I checked, Firefox didn't let you open multiple instances at a time. Some recommendations I've found involve installing an older version of Firefox somewhere to use just for WikiOnAStick (and maybe Tiddlywiki) instances. How do I add a file to Firefox's hidden white list of trusted files? So, with that, I get back to the question. The selective permitting of previously known files to rewrite themself leads me to believe that there is a white list somewhere in Firefox that tells it that those files are trusted. It is nice that they were able to do that, but they shouldn't have had to in the first case, and this doesn't help for new instances of WikiOnAStick.

#Tiddlydesktop opening install#

The Tiddlywiki guys have worked out a solution where you can install an extension to re-enable the save function for their files. But, any new WikiOnAStick or Tiddlywiki are just patently refused (by Firefox) the ability to write whatsoever. Finally, the files that I had repeatedly told older versions of Firefox to remember to permit to write themself to disk aren't asking anymore, and are just silently working. Well, now with Firefox 16, they've 'closed the security hole' that permitted those files to rewrite themselves on disk. Until recently, each time I made the first edit, the browser would pop up a 'warning' asking if I wanted to permit the file to write to disk, which I would obviously answer with 'Yes', and 'remember this setting' (and then Firefox would forget the next time the browser was closed and later restarted). I use multiple Tiddlywiki and WikiOnAStick files to store data, and those files rewrite themself on-disk each time an edit is made.