Jeremy, Thanks for looking at this innovation, and I look forward to it.
I have quickly looked at the "Browser-based local storage" plugin and see two .js tiddlers are included thus I expect I can assume then this plugin can not be dynamically loaded? The reason I ask this is, as I have raised this previously, all readonly wikis that exist out there especially tiddlywiki.com, will continue not to permit the use of temporary user tiddlers for visitors. Such temporary local storage based tiddlers allow the story, recent, and settings like the more icon to be added to the page buttons which makes tiddlywiki.com more usable as a reference. What are your thoughts on the alternatives? - Include a *disabled* "Browser-based local storage" plugin in empty (Thus can be enabled) - Install "Browser-based local storage" plugin specifically on Tiddlywiki.com - Refactor (if possible) "Browser-based local storage" plugin to be able to be dynamically installed (not recommended) - Make this use of "Browser-based local storage" plugin more prominent in documentation so more people install it in their own published wikis and thus promoting a higher level of interaction and customisation with online read only wikis. - This could include a note to delete the plugin if this behaviour is not desired (An argument for not refactoring the plugin) To me unless the "Browser-based local storage" plugin is available on read only sites the advantages conferred by the dynamic loading of plugins is further reduced as one would have to reinstall them every time one visits the site. Any way, perhaps in a separate thread, or location nominated by you, I do have some other suggested enhancements to the "Browser-based local storage" plugin to makes its use more obvious. Eg options partially Hide the standard save mechanism and have an indicator local storage is in use or available. Regards Tony On Thursday, September 12, 2019 at 6:43:52 AM UTC+10, Jeremy Ruston wrote: > > I’m pretty excited to announce that if all goes well, one of the new > features for v5.1.22 will be the ability to dynamically load/unload plugins > without needing to refresh the page. > > The catch is that this only works for plugins that do not contain any > JavaScript modules. For plugins that do contain JS modules, the behaviour > is the same as at present, with a warning message advising the user to > reload the page. The reason for this restriction is to avoid corruption due > to attempting to swap a module that is already running. Nonetheless, > there’s a huge and useful set of plugins that do not contain JS modules, > including all themes and languages. > > It’s a work in progress, and not yet merged into the prerelease: > > https://github.com/Jermolene/TiddlyWiki5/pull/4259 > > Just to be clear, this means that with the proviso above, users will be > able to: > > * Add new plugins from the plugin library without reloading > * Add new plugins via drag and drop without reloading > * Delete unneeded plugins without reloading > * Eventually, to use tools like Tinka to package plugins without requiring > a reload to test > > There’s still a fair bit to do: > > * Indicate in the plugin library which plugins will require a reload > * More testing > * Documentation > > Questions and comments welcome. > > Best wishes > > Jeremy. > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/166beba3-c6aa-4ed6-9a9a-8a75e11615f0%40googlegroups.com.
