Suppose I decide to retain an old Firefox, just to run Tiddlyfox. Tiddlywiki has code to save data to the local HTML file via Tiddlyfox. Is the plan for TW5 to retain that code for a long time, or is the plan to retire that code shortly after Firefox makes TiddlyFox obsolete?
i.e. If I continue to use TW5 with my obsolete Firefox, will I have to be careful not to update core TW5 to a version which breaks local auto-save? On Wednesday, September 20, 2017 at 10:39:58 PM UTC-4, Mark S. wrote: > > You can still use the default save, which saves as a download. I don't > think that this ability was available in the original TWC. So you can still > have your guerrilla wiki, though it takes a little more thought. Just keep > clicking save whenever you need to save. When you need to start a new > session, just find the last save in the downloads list. As a bonus, there > is automatically a trail of backups. > > I'm pretty sure (it's been a long time) that the original TWC always > needed a little bit of java code and a running JRE. It certainly did when I > first started using it. So you're memories of the good old days may be a > little bit gilded. > > Mark. > > On Wednesday, September 20, 2017 at 6:51:48 PM UTC-7, Kevin Kleinfelter > wrote: >> >> One of my main use-cases for Tiddlywiki is to capture my configuration >> when I build/rebuild a machine. In the old days, on a fresh OS, I could >> >> - login >> - download from tiddlywiki.com >> - And begin capturing my config >> >> Or I could copy my existing TW knowledge base from a backup, and capture >> my config there. The key thing is that I really didn't have to install >> stuff in order to start capturing. My knowledge base was just *there*. >> >> Then the browsers decided to get more secure. After a while, it reached >> the point where I had to install Firefox and a plugin. Not quite a >> zero-setup, but at least they were both packaged installs where I could >> just accept the default options. >> >> Now, I have to install node.js (where I can take the defaults on a >> packaged install), use npm to install tiddlywiki (and work out why it is >> giving me a "npm WARN enoent ENOENT: no such file or directory" error), >> then look up the commands to init a TW, then set up a Windows service or a >> Linux daemon to run node in the background, and *then* I can start using TW. >> >> Also in the old day, I could use TW on a fully locked-down >> corporate-controlled PC where software cannot be installed. I brought it >> in as a guerrilla wiki. I successfully defend its use as "it's just a web >> page -- you don't want to forbid people to save web pages to disk do you?" >> >> Yeah, a reasonably technical person *can* set up a node.js TW, and a >> flexible person who's not in a hurry and doesn't mind "friction" can make >> the download-and-replace-old-html-file process work. But honestly, TW5 >> doesn't have the same appeal that TWC had. It is significantly more >> complex to setup and operate. I'm probably going to migrate from TWC to >> TW5 because I can't find a one-click-install wiki that supports text and >> image and stores each page in a separate file and can (mostly) import TWC >> data. >> >> Its a wonderful creation if you want to putz with your wiki. If you just >> want to start capturing your data in a text+data wiki, it has lost its >> original simplicity. >> >> >> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/cd8bf6a8-6065-41bc-8e57-4c366581a75e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
