official plugin repository
FND
I've noticed that plugins in the default distribution* are different
from most regular plugins in that they have incomplete or outdated
meta-data.
For example, LSTP's Source field points to
http://www.tiddlywiki.com/#LegacyStrikeThroughPlugin
That tiddler doesn't exist there though. Since this plugin will probably
be dropped from the default distro sooner or later, there is no simple
way to retrieve it if needed.
If we had a repository for all "official" plugins, it would be easier to
update them (sync should do the trick), and the situation would be more
transparent overall.
I think all we need is a simple TiddlyWiki document to host these
plugins (e.g. at http://www.tiddlywiki.com/plugins.html).
Thoughts?
-- F.
PS: I accidentally posted this to [tw] at first - sorry 'bout that.
* currently CryptoFunctionsPlugin, DeprecatedFunctionsPlugin,
SparklinePlugin, and LegacyStrikeThroughPlugin
FND
> update them (sync should do the trick), and the situation would be more
> transparent overall.
There has been some confusion, so I need to clarify that this thread is
not about the plugin library, which would aggregate the plugins from
third-party authors. Instead, this is solely about the small number of
plugins that are (or used to be) provided as part of the default
TiddlyWiki distribution.
> I think all we need is a simple TiddlyWiki document to host these
> plugins (e.g. at http://www.tiddlywiki.com/plugins.html).
On further consideration, I think it's not quite as easy:
Of course we need to create a separate document on TW.com. We also need
to update the plugins' meta-data to point to this new URL.
However, I'm not entirely sure about the build process. Should the
plugins' code remain in the repository under /Trunk/core/js/[1]?
LegacyStrikeThroughPlugin's code isn't there though, so I think the
other three[2] should be separated from the core as well.
Does Cook support pulling in plugins from a different resource? (I can't
find a reference to LSTP in any recipe... !?)
Keep in mind that this plugins.html needs to be re-cooked whenever one
of the plugins has been modified.
When upgrading the TiddlyWiki core, these plugins should be treated no
different from third-party plugins. That is, they need to be updated
separately using sync. (The core-upgrade mechanism could prompt the user
to update outdated plugins - see Saq's thread[3] on that.)
-- F.
[1] http://trac.tiddlywiki.org/browser/Trunk/core/js/
[2] CryptoFunctionsPlugin, DeprecatedFunctionsPlugin, SparklinePlugin
[3] http://tinyurl.com/3xbfeg
(http://groups.google.com/group/TiddlyWikiDev/browse_thread/thread/c12866467a03f929/66073d5269f6b49f?#66073d5269f6b49f)