Hi Tobias I have now had a look at the plugin mechanism: since the hooks to 3rd party libraries are only small files, perhaps a single '3rd party plugins' plugin could be added to the core plugins -- containing these files for trusted 3rd party plugin libraries (along with a suitable warning.)
A 3rd party library could do the same -- this would create the necessary distributed network of links to available plugins. regards On Friday, 29 January 2016 12:59:53 UTC+2, Tobias Beer wrote: > > That is not exactly true. You simply need to import a tiddler that is NOT > a plugin. All it does is to define a path to the library and some field > describing that plugin resource. There can sure be a list of trusted plugin > sources that actually come shipped with the core... where user's can feel > confident that they're not going to install entirely experimental features, > but possibly / hopefully the more stable ones. > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b7eff22c-8eb1-402d-b343-773b69a6edf9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
