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.
