Unfortunately I don't think it would be possible for a LocalStorage plugin to not use Javascript. However, it could be possible to make a Chrome extension that would load this functionality for all wikis if the user desired to install such an extension. It would also be possible to enable this using a Bookmarklet which the user would click each time they load a wiki, but this would be easier to forget. The best idea is still for wikis to include this functionality for sites where it seems appropriate, assuming it has a clear way to delete tiddlers stored locally.
On Wed, Sep 11, 2019 at 9:47 PM TonyM <[email protected]> wrote: > Jeremy, > > You mention *Indicate in the plugin library which plugins will require a > reload* > > Is it not possible to determine which plugins would require this > automatically and allow it to be overridden either way with a flag on the > plugin? > > There may be cases where a Plugin need not be reloaded but the publisher > wants to trigger a reload to achieve some goal like test the ability to > save, and recall. There could be others that only become active on next > load but need not force a reload at install time. An example may be a login > method. > > I think it important to keep in mind there are an increasing number of > macro solutions out there that need never pe published as Plugins of the > traditional kind. What you are proposing here should make the plugin > mechanism more flexible encouraging such macro only solutions to also be > packaged as plugins (That can be dynamically loaded). Perhaps we need to > indicate in the plugins if they need reload or not before install. > > Also the local browser storage can facilitate a reload on top of read only > sites (If installed) - not withstanding its other limitations. > > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/7b2cd683-8ee1-45d4-bd08-0591284313e9%40googlegroups.com > <https://groups.google.com/d/msgid/tiddlywiki/7b2cd683-8ee1-45d4-bd08-0591284313e9%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSRX9NLQxiF4EcpSgPtsDcx4zXb%2B4yk%3DEVPi88ED5oavng%40mail.gmail.com.
