Thanks for reply Jeremy! > 1) Could upgrading be done via the plugin library, i.e upgrade the $:/core > plugin just like any other plugin? > > > OK, so the process would be to pull in the new core plugin, and then save > changes. The trouble is that at that point the new core isn’t active, and > so the templates used for saving would be the templates from the old core. >
It would be *superior *to be able to upgrade like this so how about this idea: Importing the core could also import an extra set of the saving templates, i.e not shadow tids! These can be imported without reload and will immediately overwrite the *current *saving template shadow tids and they will have effect right away (...right?). These loose tempaltes can even be used for other stuff such as a presentation of the release notes with an "OK, got it" button at the bottom that deletes the extra tiddlers, making the core shadow saving templates kick in again. (Or maybe the custom refresh button that one should click after importing a plugin can be made to delete those temporary saving tids as some last step?) A perhaps hidden design goal of the current upgrade process is that it can > upgrade broken TiddlyWikis because it only relies on being able to import > tiddlers from the old file. This means that if we ever released a core > version that was broken we would still be able to upgrade it. > Good but/and it would serve as a useful repair tool when someone has messed up the core (which is pretty rare, no?). And this also feels like something that is better if accessed viea ones own TW. I just did a quick test. I put this in a TW (on tiddlyspot) <iframe src="http://tiddlywiki.com/upgrade.html"; width="100%" height="600px"></iframe> It works to drag'n drop a tiddler onto this iframe, at least in FF (not chrome). I figure that if one needs to repair ones TW, and if the problems are not preventing it, one could drag *all* content tiddlers (via one link, like the new drag'n drop pills) onto this. When repairing, it does seem justified to have it download but it would be neat if the various saving options were presented there too. ... Anyway, the more important issue is the first one about being able to upgrad like importing any other plugin. This would probably also make people more aware of plugins and plugin library matters. I've found that I barely ever go to the plugin library and therefore don't think much about how it could be improved. <:-) -- 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 https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/20de8a63-a07e-494f-988f-9ff91eff3a42%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
