Hi Arlen What's keeping us from using the java file/tiddlyfox to handle all the file > stuff, or is this already the case? Also, the idea of a backstage is so you > can do some stuff in case something goes really awry with the css and html, > but maybe there is another way of doing that. What I liked about the > backstage was that it was outside of the content wrapper, so any changes to > the CW wouldn't affect it. >
TW5 won't use TiddlySaver because Java is a dying technology (at least on the desktop), and is increasingly considered dangerous from a vulnerability standpoint. But it does use TiddlyFox if it's present, and hopefully there will be equivalents for other browsers. But it's important that TW5 work as well as it can on naked browsers, both desktop and mobile. Best wishes Jeremy > > On Mon, Mar 25, 2013 at 10:27 AM, Tobias Beer <[email protected]>wrote: > >> Hi Jeremy, >> >> Indeed, the plan is to add an import mechanism that will then be used for >>> upgrading. Hopefully quite soon; it's certainly a necessity if we want >>> people to be able to conveniently test it. >> >> >> Will this replace the classic TiddlyWiki way to upgrade TiddlyWiki via >> some backstage upgrade wizard? >> >> I would prefer that and see classic upgrading rather as a nice-to-have >> plugin, which requires the conscious decision first of installing some >> UpgradePlugin. >> >> I would argue that... >> >> 1. upgrading via importing is a viable option and not much harder to >> do that having an upgrade wizard... while also making you create a backup >> first, before you can give the old file name to the new version >> 2. for many users / use cases, keeping up with core upgrades really >> isn't necessary in the sense of "never change a running system (unless you >> really have to)" >> - from my experiences with linux, for example, the desire to >> constantly upgrade all to quickly brings way more trouble than it's >> actually worth >> 3. importing actually requires you to create a new document while >> upgrading does not, the latter being a problem when things go wrong >> >> >> ~ >> >> On the other hand, does TW5 even have a backstage area? I would much >> prefer if it didn't, because it's yet another UI component that is actually >> not needed and comes with a bunch of constraints to cater for. >> >> Cheers, Tobias. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "TiddlyWikiDev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWikiDev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Jeremy Ruston mailto:[email protected] -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
