Further ideas Perhaps a mechanism to save a filtered set of tiddlers from memory or local storage to a filename based on user ID (in the file folder, or on the server) and looking for this file on load/login to restore said tiddlers would help with multiple users working on top of a served wiki. It would add a persistent alternative to local storage, by using actual storage.
If additional export/load files where possible it would be easy to build wikis which; - Can interrogate a server for check in and check out status - A master wiki mode where the "owner" could load user tiddlers and selectively incorporate them into the master wiki. - Build a messaging system between multiple Wikis by loading a library of message tiddlers from other users or wikis, and writing responses back to the current users messages library. Regards Tony On Saturday, July 13, 2019 at 10:46:23 AM UTC+10, TonyM wrote: > > Mat, > > This idea has merit, and it has being discussed previously. The Start to > understanding this is > https://tiddlywiki.com/#Installing%20a%20plugin%20from%20the%20plugin%20library > I believe others have built their own libraries. > > and related information includes > > - The system tag <https://tiddlywiki.com/#SystemTags> > $:/tags/PluginLibrary marks the plugin library > - WidgetMessage: tm-load-plugin-from-library > > And you can download https://tiddlywiki.com/library/v5.1.11/index.html to > see what it looks like inside a plugin library. > > One thing that loading plugins does is force a save and reload, which > regular tiddlers and bundles often do not. So if the library mechanisium is > extended beyond plugins this should make this "import" occur silently on a > click. Because of the WidgetMessage: tm-load-plugin-from-library can be > used in an action widget we should be able to use it in startup actions and > according to other triggers, one trigger that would be great is on a change > in date stamp on the library file. > > Perhaps we could have tiddler Libraries in addition to plugin libraries. > > The corollary is saving or exporting to the library file, I would be nice > if on a trigger we can save a filtered list of tiddlers to a named library > file, and where a save mechanism is available use that, for example if I > could authorise my Wiki on top of tw-reciever (PHP saver) to save to > "library name", or at worst resort to the download saver (undesirable). > > I as yet do not know how to hack the plugins from library method as I do > the interactive import function, I do not know how to intervene and choose > to add a prefix to imported tiddlers and other selective processing. > However with a controlled export to a library we can manage around this. > > *Perhaps some of our team mates can throw some light on this. With a > little help we could possibly hack together a solution that may demonstrate > its value.* > > Regards > Tony > > > On Saturday, July 13, 2019 at 6:00:56 AM UTC+10, Mat wrote: >> >> Is tiddlywiki.com set up in some special way that enables this official >> plugin library to serve tiddlers from it? >> >> Assuming it is, why can't this be built into native TW so that people can >> fetch tiddlers from each others wikis? >> >> <:-) >> > -- 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/55a22ae5-064e-4262-af1a-1a447e33cf93%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
