Birthe et al..
Libraries are tiddlers that point to libraries. Currently libraries are
focused on plugins, not other types of tiddlywiki object. However we could
have a library of community libraries. Choose a library install it, then go
to plugins get more and select the recently installed library tab. I would
suggest enhancing the library tiddlers a little to include more details or
keywords to help find what is in an installed library. It would not be
harmful if libraries also contain an updated library tiddler and version
number so it too could be updated from a library.
- Community library of libraries
- To install library tiddlers from the community
- Contains an update library tiddler if necessary
- Caviet that the content in controlled by others and to be careful
in your choice/backup or test on an empty wiki first
- Each community members library
- Exists at a URL they can control and update allowing the latest
version to be available to any one with the library tiddler installed
- Can be opened and searched for plugins and ideally also macros, or
test date tiddler packages
The community libraries of libraries can be updated occasionally after
applying the library tiddler update contained in the library or when new
ones are submitted.
*Library usage methods to consider*
- I have all but finished in a single file wiki a way to generate
libraries from selected plugins. see here
<https://groups.google.com/forum/?hl=en#!topic/tiddlywikidev/7l0irgLJOys>,
I am frozen at the moment dealing with how to pack tiddler titles that not
only store in the zip but work when hosted online after expansion of the
ZIP. This would democratise the library creation to support my suggestion
of a library of libraries.
- My Playground wiki here
<https://anthonymuscio.github.io/playground.html> demonstrates an online
tiddlywiki, with multiple plugin libraries available, see get more plugins,
as it has local storage activated you can download a plugin and reload
without saving the wiki. It allows you to preview/test any plugin, then
download the plugin or drag and drop it you your on wiki.
- Most people could be encouraged to do what I do and have a staging
place for plugins. I drop all plugins I acquire on a Bob wiki and disable
them, that is my first repository I refer to when looking for plugins,
where I also have additional notes for each plugin, including links to
source and demo pages if they were not provided. If we had the community
library of libraries I would put that on my local plugin wiki. When I drag
and drop a disabled plugin it is enabled on the target wiki.
Whilst libraries may be the way to go others are available.
- I have drag-able package Icons that can be used to export or drag and
drop bundles of tiddlers from a wiki.
- We build a community registry of tiddlywiki sites, not unlike tiddly,
or extending TiddlyWiki Toolmap
<https://dynalist.io/d/zUP-nIWu2FFoXH-oM7L7d9DM> to permit community
submissions of wikis and libraries, seperate from the current "curated"
lists.
Regards
Tones
On Wednesday, August 12, 2020 at 12:59:58 AM UTC+10, Birthe C wrote:
>
> TT,
>
> Not many has created a plugin library. I think it is due to them having to
> change the way they work to do so.
> Not at anytime will everyone be on github either.
>
> I wonder if every plugin writer had a plugin library, how would you be
> able to find anything from the plugin tab in control panel,
>
> It is kind of like the Community Search. Not much to find there. Tobias
> and Jed - yes...and others got connected due to links from their pages. Not
> so simple after all.
> I wonder could it still be used today if people knew how to?
>
>
> Birthe
>
--
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/709c070b-101b-4c09-a004-3a4d093ea0b8o%40googlegroups.com.
