Plugins Web Dig Findings

While looking for information for TWikiDevelopmentStartingKit, I went to the Plugins web and checked all the non-plugin topics. Here are my findings.

-- RafaelAlvarez - 03 Nov 2004

Non-Consolidated topics

Topics with good ideas, but nothing concrete

• ExperiencesSubmittingPlugins
• InstalledOnTWikiOrg
• MyRecentChanges
• TemplateVersusTopicTextProcessing
• TWikiPluginAPI

Delete Candidates?

These pages seems to be DeleteMe candidates. I'll wait a week before putting the TWikiBrand on them.

• DesignQuality
• DoYouWantToHelp
• ExampleUsefulness
• InterWikiGreedy
• HowToDocumentPluginPerformance (this can be replaced by AthensMarks benchmarks)
• PluginAPIGetVersion
• PluginDependencies
• PluginCvsToolsAddOn
• PluginPackagingHowTo
• PluginsHowTo
• PluginsWithNonFuncCode
• SkinFAQ
• PluginCvsToolsAddOn
• Plugins/InstalledPluginsShouldBeAutomatic

Lost & Found Perls

There are contribution that got lost in the pile of rubble.

It would also be quite useful to have the plugin's associated .txt page added to the TWikiPlugins page when it's installed, or alternatively added to a plugins web as has recently semi-surfaced on twiki.org. If a plugin's options can be configured via it's page, then so much the better as it exposes it to (possibly group constrained set of) users for configuration.

-- DavidLeBlanc - 17 Jul 2001

Skipping Rendering Stages

I see by the StepByStepRenderingOrder that rendering plugins will get called at least 3 times (%text%, %metadata%, %template%). Is there anyway way to flag steps as "clean"? e.g. No need to call me here, I don't do metadata or templates, only text?

-- MattWilkie - 02 Feb 2004

No. And it's bloody difficult to find out why the handler was called (which phase).

-- CrawfordCurrie - 04 Nov 2004