I wonder if there is a way to allow use to search the contents of libraries, even if we need to generate an index? The two you gave me and the relink one currently contain only one plugin.
@TW_Tones, well I dunno. Yes, IF it were easy for you.
I’d say that IF Plugin Library use got more uptake that summary data on each library might be useful?
One of those summary items being “no of plugins” (For instance SoundCite has 1 and the CPL currently has 303 — that is some kind of difference! )
Could do this like a curator but ideally seek a summary from the Library owners.
There maybe a way to programmatically extract contents and make that searchable.
Agreed a manual count will be a good start
Sure
Yes, I have an idea here that you need not install the library in a wiki but extract a plugin on this wiki and move the plugin. However the libraries have the advantage of detecting updates.
With the local storage active it would retain a set of plugins commonly used by you. A kind of holding bay.
IMO it is far better that the AUTHORS write the summaries.
Why? Because curation, though actually better, is difficult to maintain unless we had a person who loves that kind of thing. Curating software (ongoing) that changes is a somewhat thankless task ?
The Chinese library is a good case to think about since it references over 300 sources. HOW would one document that???
I do, but they can already include details in the library tiddler, however I think the library tiddler is not updated “over the wire”, like the plugins.
I am willing, since libraries themselves don’t change or new ones don’t appear too often, at least up to now. The Content of the library and plugins remain in the control of the publisher.
I would raise a ongoing discussion that would allow users to submit libraries via talk.tiddlywiki
I believe as soon as we build a way to publish plugin libraries from a single file wiki there could be a boom in libraries.
Especially to also share macros - I have already secured macros.tiddlyhost.com for some ideas there, not even started yet.
From my point of view the mechanism of it is lightweight. It works well.
It is maybe not as known yet as it might be.
IMO it solves a bunch of issues that TW has on being informationally fragmented on how to enhance it.
In short, what you have done is a definite step in a good direction!