Hi Mat > 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?).
It’s not just templates, but also JS modules; the saving would be under the control of the old JS files, and there’s no way for us to update them before the save operation. > Good but/and it would serve as a useful repair tool when someone has messed > up the core (which is pretty rare, no?). It’s not just about users messing the core up, but also about the developers messing up; we need to be able to recover from publishing a faulty version of TiddlyWiki. You may respond that we could have a separate upgrade process that we direct users to when such a failure occurs, but then I’d need to maintain two different upgrade processes. > 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. We could go further, and use some of the techniques from the plugin library: host the upgrade page in a hidden iframe within the TiddlyWiki, and use window.postMessage to send it the tiddlers for the upgrade, and then send another message to tell it to save itself. But we’re back where we started, with the reliability of the upgrade depending on the integrity of the wiki being upgraded. > 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. Upgrading is not exactly like importing any other plugin, that’s the point :) A similar argument can be made that the current upgrade process encourages people to discover and think about the way that wikis can be imported into other wikis... Best wishes Jeremy > > > <:-) > > -- > 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] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/tiddlywikidev > <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 > > <https://groups.google.com/d/msgid/tiddlywikidev/20de8a63-a07e-494f-988f-9ff91eff3a42%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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/CD60F785-5535-42B1-BD48-B5CB7FD784C2%40gmail.com. For more options, visit https://groups.google.com/d/optout.
