Hi Tobias
> 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. > Yes, the only way to upgrade the single file edition will be by importing content into a later version. There are some opportunities to make the experience simpler: - Drag and drop: one could visit tiddlywiki.com/empty.html (or a downloaded copy), and then drag a TiddlyWiki *.html file onto the browser window from Explorer/Finder. TiddlyWiki would then import the tiddlers into an empty TiddlyWiki and ask the browser to download it. The end result would be an upgraded TiddlyWiki file, but the users' data wouldn't be transmitted to tiddlywiki.com. - Upgrade button: we can also provide an "upgrade" button within a TiddlyWiki that basically opens tiddlywiki.com/empty.html in a new tab/window with a # portion of the URI specifying the data to be imported. The user could then preview their imported data before downloading it. > 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 > > In truth there's not much difference - in classic TW (and in the suggestions above for TW5) the upgrade wizard is just a front end to the import procedure. > > 1. 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 > > I would be inclined to agree that upgrade fever can be counterproductive. I'd certainly steer clear of automatically doing upgrade checks when TW5 starts up. However, in the early days of TW5 there will likely be rapid development with lots of changes and new features that people will understandably want to be able to take advantage of. > > - > 1. 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. > As Arlen notes, the point of the backstage area is to be a consistent area of the user interface that isn't readily affected by customisation. It wasn't really intended to be the primary user interface, more of a fallback if one had messed up the PageTemplate. Best wishes Jeremy > > Cheers, Tobias. > -- 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.
