@telumire I am amazed and grateful you created this, I have played with the example library and it all seems quite usable.
- For my personal use I can go strait ahead and use it
- I had researched something similar in the past, and asked the community with no responce.
Why so good?
We can now democratise the use of libraries for pubilc or personal use with the advantage that such a distribution method would allow changes to be detected and reinstalled.
It seems to me your solution may benifit from the following and I would be happy to submit some content if you are interested;
- A high level technical description of the solution
- I may be ble to do this but would need a technical review
- Some simple point and click named library creation and select plugins
- Add some content to support users arriving at the plugin library wiki
- Including the library owner
- A guide to responcible library publishing
Uses and futures
- I wonder if we can use this to distribute our own plugin/content from file:// wikis ?
- It would be nice to introduce the ability to drive the assetList via a confgurable filter. Allowing sophisticated sites, such as an edition to use multiple plugins but only add specific plugins to the library.
Questions
- How can we include Themes and Languages?
- Why is the PluginLibraryScript introduced via TopHead rather than installed as a plugin?
- So it is not in the plugin list? A method worth documenting.
- Could we support multiple libraries from the same site? I expect not as the url to the library is the site, I expect thisisrelated to the last question, the HTML needs to be read without loading in a browser.
I have more ideas I will keep to myself for now, so as to not be too verbose. Hint other tiddlers via plugin mechanisium such as data tiddlers, additional plugin types