Difference: TWikiPlugins (32 vs. 33)

Revision 3316 May 2007 - Main.TWikiContributor

Line: 1 to 1
Deleted:
<
<
 
Changed:
<
<

TWiki Plugins

>
>

TWiki Plugins

  Add functionality to TWiki with readily available Plugins; create Plugins based on APIs
Added:
>
>
 

Overview

You can add Plugins to extend TWiki functionality, without altering the core code. A plug-in approach lets you:

Line: 38 to 39
 

On-Site Pretesting

Changed:
<
<		The recommended approach to testing new Plugins before making them public is to create a second local TWiki installation, and test the Plugin there. You can allow selected users access to the test area. Once you are satisifed that it won't compromise your main installation, you can install it there as well.
>
>		The recommended approach to testing new Plugins before making them public is to create a second local TWiki installation, and test the Plugin there. You can allow selected users access to the test area. Once you are satisfied that it won't compromise your main installation, you can install it there as well.
  InstalledPlugins shows which Plugins are: 1) installed, 2) loading properly, and 3) what TWiki:Codev.PluginHandlers they invoke. Any failures are shown in the Errors section. The %FAILEDPLUGINS% variable can be used to debug failures. You may also want to check your webserver error log and the various TWiki log files.

Some Notes on Plugin Performance

Changed:
<
<		The performance of the system depends to some extent on the number of Plugins installed and on the Plugin implementation. Some Plugins impose no measurable performance decrease, some do. For example, a Plugin might use many Perl libraries that need to be initialized with each page view (unless you run mod_perl). You can only really tell the performance impact by installing the Plugin and by measuring the performance with and without the new Plugin. Use the TWiki:Plugins.PluginBenchmarkAddOn, or test manually with the Apache ab utility. Example on Unix:
time wget -qO /dev/null /twiki/bin/view/TWiki/AbcPlugin
>
>		The performance of the system depends to some extent on the number of Plugins installed and on the Plugin implementation. Some Plugins impose no measurable performance decrease, some do. For example, a Plugin might use many Perl libraries that need to be initialized with each page view (unless you run mod_perl). You can only really tell the performance impact by installing the Plugin and by measuring the performance with and without the new Plugin. Use the TWiki:Plugins.PluginBenchmarkAddOn, or test manually with the Apache ab utility. Example on Unix:
time wget -qO /dev/null /twiki/bin/view/TWiki/AbcPlugin
  TIP If you need to install an "expensive" Plugin, but you only need its functionality only in a subset of your data, you can disable it elsewhere by defining the %DISABLEDPLUGINS% TWiki variable.
Changed:
<
<		Define DISABLEDPLUGINS to be a comma-separated list of names of plugins to disable. Define it in Main.TWikiPreferences to disable those plugins everywhere, in the WebPreferences topic to disable them in an individual web, or in a topic to disable them in that topic. For example,
>
>		Define DISABLEDPLUGINS to be a comma-separated list of names of plugins to disable. Define it in Main.TWikiPreferences to disable those plugins everywhere, in the WebPreferences topic to disable them in an individual web, or in a topic to disable them in that topic. For example,
 
   * Set DISABLEDPLUGINS = SpreadSheetPlugin, EditTablePlugin
Line: 64 to 65
 

Plugin Evaluation Order

Changed:
<
<		By default, TWiki executes Plugins in alphabetical order on Plugin name. It is possible to change the order, for example to evaluate database variables before the speadsheet CALCs. This can be done with {PluginsOrder} in the Plugins section of configure.
>
>		By default, TWiki executes Plugins in alphabetical order on Plugin name. It is possible to change the order, for example to evaluate database variables before the spreadsheet CALCs. This can be done with {PluginsOrder} in the Plugins section of configure.
 

Plugin-Specific Settings

Line: 76 to 77
  Plugin status variables let you list all active Plugins wherever needed.
Added:
>
>		This site is running TWiki version TWiki-4.2.2, Wed, 06 Aug 2008, build 17396, Plugin API version 1.2

 

%ACTIVATEDPLUGINS%

On this TWiki site, the enabled Plugins are: SpreadSheetPlugin, AlbumOfSnapsPlugin, ApprovalPlugin, AttachmentListPlugin, CaptchaPlugin, CommentPlugin, CounterPlugin, EditTablePlugin, EmptyPlugin, ImageGalleryPlugin, ImagePlugin, InterwikiPlugin, NewsPlugin, PreferencesPlugin, RenderListPlugin, SendEmailPlugin, SlideShowPlugin, SmiliesPlugin, TablePlugin, TagMePlugin, TinyMCEPlugin, TopicTranslationsPlugin, TwistyPlugin, WysiwygPlugin.

%PLUGINDESCRIPTIONS%

  • SpreadSheetPlugin (any TWiki, $Rev: 17387 (11 Aug 2008) $): Add spreadsheet calculation like "$SUM( $ABOVE() )" to TWiki tables and other topic text
  • AlbumOfSnapsPlugin (Dakar, $Rev: 10613 (12 Dec 2008) $):
  • ApprovalPlugin (1.0, $Rev: 3923 (2009-05-16) $): Defines a set of states for one more or topics, with each state requiring approval by one or more users.
  • AttachmentList: (disabled)
  • AttachmentListPlugin (1.2.6, $Rev: 17172 (28 Jul 2008) $): Displays a formattable list of topic attachments, anywhere in a topic.
  • BatchUploadPlugin: (disabled)
  • CaptchaPlugin (Dakar, 1.5-pre4): To prevent automated bots from spamming
  • CommentPlugin (03 Aug 2008, $Rev: 17302 (11 Aug 2008) $): Allows users to quickly post comments to a page without an edit/preview/save cycle
  • CounterPlugin (Dakar, $Rev: 14404 (12 Dec 2008) $): This plugin maintains the Visitor Count for the site.
  • EditTablePlugin (4.8.4, $Rev: 17302 (11 Aug 2008) $): Edit TWiki tables using edit fields, date pickers and drop down boxes
  • EmptyPlugin (TWiki-4.2, $Rev: 15942 (11 Aug 2008) $): Empty Plugin used as a template for new Plugins
  • ImageGalleryPlugin (3.72, $Rev: 17034 (16 Jul 2008) $): Displays image gallery with auto-generated thumbnails from attachments
  • ImagePlugin (2010-08-01, $Rev: 19301 (2010-08-01) $): Control the display and alignment of images using an easy syntax
  • InterwikiPlugin (03 Aug 2008, $Rev: 14913 (17 Sep 2007) $): Link ExternalSite:Page text to external sites based on aliases defined in a rules topic
  • MultiEditPlugin: (disabled)
  • NewsPlugin (Dakar, $Rev: 15565 (12 Dec 2008) $): %NEWS% generates a short headlines topic from a list of news
  • PreferencesPlugin (TWiki-4.2, $Rev: 15487 (11 Aug 2008) $): Allows editing of preferences using fields predefined in a form
  • RenderListPlugin (2.0, $Rev: 16235 (11 Aug 2008) $): Render bullet lists in a variety of formats
  • SendEmailPlugin (1.2.2, $Rev: 17666 (12 Dec 2008) $): Allows to send e-mail through an e-mail form
  • SlideShowPlugin (02 Aug 2008, $Rev: 17260 (11 Aug 2008) $): Create web based presentations based on topics with headings.
  • SmiliesPlugin (Dakar, $Rev: 16049 (11 Aug 2008) $): Render smilies as icons, like smile for  :-) or eek! for  :eek:
  • TablePlugin (1.034, $Rev: 17367 (11 Aug 2008) $): Control attributes of tables and sorting of table columns
  • TagMePlugin (TWiki 4, 1.046): Tag wiki content collectively to find content by keywords
  • TinyMCEPlugin (03 Aug 2008, $Rev: 17302 (11 Aug 2008) $): Integration of TinyMCE? with WysiwygPlugin
  • TopicTranslationsPlugin (Dakar, $Rev: 15568 (12 Dec 2008) $): Manages a topic's translations into several languages.
  • TwistyPlugin (1.4.10, $Rev: 15653 (19 Nov 2007) $): Twisty section JavaScript library to open/close content dynamically
  • WysiwygPlugin (03 Aug 2008, $Rev: 17359 (11 Aug 2008) $): Translator framework for Wysiwyg editors
Added:
>
>
 

%FAILEDPLUGINS%

PluginErrors
SpreadSheetPlugin none
AlbumOfSnapsPlugin none
ApprovalPlugin none
AttachmentList? 
TWiki::Plugins::AttachmentList could not be loaded.  Errors were: 
Can't locate TWiki/Plugins/AttachmentList.pm in @INC (@INC contains: /var/www/twiki422/lib . /etc/perl /usr/local/lib/perl/5.10.0 /usr/local/share/perl/5.10.0 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl /var/www/twiki422/lib/CPAN/lib//arch /var/www/twiki422/lib/CPAN/lib//5.10.0/x86_64-linux-gnu-thread-multi /var/www/twiki422/lib/CPAN/lib//5.10.0 /var/www/twiki422/lib/CPAN/lib/) at (eval 47) line 1.
BEGIN failed--compilation aborted at (eval 47) line 1.

----
AttachmentListPlugin none
BatchUploadPlugin 
TWiki::Plugins::BatchUploadPlugin could not be loaded.  Errors were: 
Can't locate Archive/Zip.pm in @INC (@INC contains: /var/www/twiki422/lib . /etc/perl /usr/local/lib/perl/5.10.0 /usr/local/share/perl/5.10.0 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl /var/www/twiki422/lib/CPAN/lib//arch /var/www/twiki422/lib/CPAN/lib//5.10.0/x86_64-linux-gnu-thread-multi /var/www/twiki422/lib/CPAN/lib//5.10.0 /var/www/twiki422/lib/CPAN/lib/) at /var/www/twiki422/lib/TWiki/Plugins/BatchUploadPlugin.pm line 28.
BEGIN failed--compilation aborted at /var/www/twiki422/lib/TWiki/Plugins/BatchUploadPlugin.pm line 28.
Compilation failed in require at (eval 51) line 1.
BEGIN failed--compilation aborted at (eval 51) line 1.

----
CaptchaPlugin none
CommentPlugin none
CounterPlugin none
EditTablePlugin none
EmptyPlugin none
ImageGalleryPlugin none
ImagePlugin none
InterwikiPlugin none
MultiEditPlugin 
TWiki::Plugins::MultiEditPlugin could not be loaded.  Errors were: 
Can't locate TWiki/Contrib/EditContrib.pm in @INC (@INC contains: /var/www/twiki422/lib . /etc/perl /usr/local/lib/perl/5.10.0 /usr/local/share/perl/5.10.0 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl /var/www/twiki422/lib/CPAN/lib//arch /var/www/twiki422/lib/CPAN/lib//5.10.0/x86_64-linux-gnu-thread-multi /var/www/twiki422/lib/CPAN/lib//5.10.0 /var/www/twiki422/lib/CPAN/lib/) at /var/www/twiki422/lib/TWiki/Plugins/MultiEditPlugin.pm line 28.
BEGIN failed--compilation aborted at /var/www/twiki422/lib/TWiki/Plugins/MultiEditPlugin.pm line 28.
Compilation failed in require at (eval 81) line 1.
BEGIN failed--compilation aborted at (eval 81) line 1.

----
NewsPlugin none
PreferencesPlugin none
RenderListPlugin none
SendEmailPlugin none
SlideShowPlugin none
SmiliesPlugin none
TablePlugin none
TagMePlugin none
TinyMCEPlugin none
TopicTranslationsPlugin none
TwistyPlugin none
WysiwygPlugin none
HandlerPlugins
afterEditHandlerWysiwygPlugin
afterSaveHandlerTagMePlugin
beforeAttachmentSaveHandlerApprovalPlugin
beforeCommonTagsHandlerApprovalPlugin
EditTablePlugin
PreferencesPlugin
TopicTranslationsPlugin
WysiwygPlugin
beforeEditHandlerApprovalPlugin
TinyMCEPlugin
WysiwygPlugin
beforeMergeHandlerWysiwygPlugin
beforeSaveHandlerApprovalPlugin
CaptchaPlugin
CommentPlugin
NewsPlugin
WysiwygPlugin
commonTagsHandlerSpreadSheetPlugin
AlbumOfSnapsPlugin
CaptchaPlugin
CommentPlugin
CounterPlugin
EditTablePlugin
ImageGalleryPlugin
ImagePlugin
SlideShowPlugin
SmiliesPlugin
TagMePlugin
TopicTranslationsPlugin
initPluginSpreadSheetPlugin
AlbumOfSnapsPlugin
ApprovalPlugin
AttachmentListPlugin
CaptchaPlugin
CommentPlugin
CounterPlugin
EditTablePlugin
EmptyPlugin
ImageGalleryPlugin
ImagePlugin
InterwikiPlugin
NewsPlugin
PreferencesPlugin
RenderListPlugin
SendEmailPlugin
SlideShowPlugin
SmiliesPlugin
TablePlugin
TagMePlugin
TinyMCEPlugin
TopicTranslationsPlugin
TwistyPlugin
WysiwygPlugin
modifyHeaderHandlerWysiwygPlugin
postRenderingHandlerEditTablePlugin
PreferencesPlugin
WysiwygPlugin
preRenderingHandlerInterwikiPlugin
SmiliesPlugin
TablePlugin
startRenderingHandlerRenderListPlugin
WysiwygPlugin
This handler is deprecated - please check for updated versions of the plugins that use it!
27 plugins

Line: 111 to 117
 
  • For example, use an eval block like this:
    eval { require IPC::Run }
    return "<font color=\"red\">SamplePlugin: Can't load required modules ($@)</font>" if $@;
Changed:
<
<
  • You can use a flag to avoid running the initialization twice
  • The TWiki:Plugins.PluginBenchmarkAddOn comes in handy to measure and fine-tune the performance of your Plugin
>
>
  • Keep the main plugin package as small as possible; create other packages that are loaded if and only if they are used. For example, create sub-packages of BathPlugin in lib/TWiki/Plugins/BathPlugin/.
  • Avoid using preferences in the plugin topic; set $NO_PREFS_IN_TOPIC if you possibly can, as that will stop TWiki from reading the plugin topic for every page. Use Config.spec instead.
  • Use registered tag handlers
  • Measure the performance to see the difference
 
Changed:
<
<

Plugin Version Detection

>
>

Version Detection

 
Changed:
<
<		To eliminate the incompatibility problems bound to arise from active open Plugin development, a Plugin versioning system is provided for automatic compatibility checking.
>
>		To eliminate the incompatibility problems that are bound to arise from active open Plugin development, a Plugin versioning system is provided for automatic compatibility checking.
 
Changed:
<
<
  • All modules require a $VERSION='0.000' variable, beginning at 1.000.
>
>
  • All plugin packages require a $VERSION variable. This should be an integer, or a subversion version id.
 
Changed:
<
<
  • The initPlugin handler should check all dependencies and return TRUE if the initialization is OK or FALSE if something went wrong.
    • The Plugin initialization code does not register a Plugin that returns FALSE (or that has no initPlugin handler).
>
>
  • The initPlugin handler should check all dependencies and return 1 if the initialization is OK or 0 if something went wrong.
    • The Plugin initialization code does not register a Plugin that returns 0 (or that has no initPlugin handler).
 
  • $TWiki::Plugins::VERSION in the TWiki::Plugins module contains the TWiki Plugin API version, currently 1.2.
    • You can also use the %PLUGINVERSION{}% variable to query the Plugin API version or the version of installed Plugins.
Line: 142 to 150
 

Anatomy of a Plugin

Changed:
<
<		A basic TWiki Plugin consists of two elements:
>
>		A (very) basic TWiki Plugin consists of two files:
 
Changed:
<
<
  • a Perl module, ex: MyFirstPlugin.pm
  • a documentation topic, ex: MyFirstPlugin.txt
>
>
  • a Perl module, e.g. MyFirstPlugin.pm
  • a documentation topic, e.g. MyFirstPlugin.txt
 
Changed:
<
<		The Perl module can be a block of code that connects with TWiki alone, or it can include other elements, like other Perl modules (including other Plugins), graphics, TWiki templates, external applications (ex: a Java applet), or just about anything else it can call.
>
>		The Perl module can be a block of code that talks to with TWiki alone, or it can include other elements, like other Perl modules (including other Plugins), graphics, TWiki templates, external applications (ex: a Java applet), or just about anything else it can call.
 In particular, files that should be web-accessible (graphics, Java applets ...) are best placed as attachments of the MyFirstPlugin topic. Other needed Perl code is best placed in a lib/TWiki/Plugins/MyFirstPlugin/ directory.

The Plugin API handles the details of connecting your Perl module with main TWiki code. When you're familiar with the Plugin API, you're ready to develop Plugins.

Added:
>
>		The TWiki::Plugins.BuildContrib module provides a lot of support for plugins development, including a plugin creator, automatic publishing support, and automatic installation script writer. If you plan on writing more than one plugin, you probably need it.
 

Creating the Perl Module

Copy file lib/TWiki/Plugins/EmptyPlugin.pm to <name>Plugin.pm. The EmptyPlugin.pm module contains mostly empty functions, so it does nothing, but it's ready to be used. Customize it. Refer to the Plugin API specs for more information.

Line: 162 to 172
 $var = MyFirstPlugin? ::Attrs->new();
Deleted:
<
<

Measuring and Improving the Plugin Performance

A high quality Plugin performs well. You can use the TWiki:Plugins.PluginBenchmarkAddOn to measure your TWiki:Plugins.PluginBenchmarks. The data is needed as part of the Documentation Topic.

See also Hints on Writing Fast Plugins.

 

Writing the Documentation Topic

Changed:
<
<		The Plugin documentation topic contains usage instructions and version details. It serves the Plugin files as FileAttachments for downloading. (The doc topic is also included in the distribution package.) To create a documentation topic:
>
>		The Plugin documentation topic contains usage instructions and version details. It serves the Plugin files as FileAttachments for downloading. (The doc topic is also included in the distribution package.) To create a documentation topic:
 
  1. Copy the Plugin topic template from TWiki.org. To copy the text, go to TWiki:Plugins/PluginPackage and:
    • enter the Plugin name in the "How to Create a Plugin" section
    • click Create
    • select all in the Edit box & copy
    • Cancel the edit
Changed:
<
<
    • go back to your site to the TWiki web
>
>
    • go back to your site to the TWiki web
 
    • In the GoBox enter your Plugin name, for example MyFirstPlugin, press enter and create the new topic
    • paste & save new Plugin topic on your site
  1. Customize your Plugin topic.
Line: 197 to 200
  Plugin Settings: <Description and settings for custom Plugin %VARIABLES%, and those required by TWiki.>"
Changed:
<
<
  • Plugins Preferences <If user settings are needed, explain... Entering values works exactly like TWikiPreferences and WebPreferences: six (6) spaces and then:>"
>
>
  • Plugins Preferences <If user settings are needed, explain... Entering values works exactly like TWikiPreferences and WebPreferences: six (6) spaces and then:>"
 
    • Set <EXAMPLE = value added>

Plugin Installation Instructions: <Step-by-step set-up guide, user help, whatever it takes to install and run, goes here.>"

Line: 221 to 224
 
    • data/TWiki/MyFirstPlugin.txt
    • pub/TWiki/MyFirstPlugin/uparrow.gif
Added:
>
>

Measuring and Improving the Plugin Performance

A high quality Plugin performs well. You can use the TWiki:Plugins.PluginBenchmarkAddOn to measure your TWiki:Plugins.PluginBenchmarks. The data is needed as part of the Documentation Topic.

See also Hints on Writing Fast Plugins.

 

Publishing for Public Use

Line: 245 to 255
 

Plugin Internal Data

Changed:
<
<		You can create a Plugin "work area" using the TWiki::Func::getWorkArea() function, which gives you a persistant directory where you can store data files. By default they will not be web accessible. The directory is guaranteed to exist, and to be writable by the webserver user. For convenience, TWiki::Func::storeFile() and TWiki::Func::readFile() are provided to persistently store and retrieve simple data in this area.
>
>		You can create a Plugin "work area" using the TWiki::Func::getWorkArea() function, which gives you a persistent directory where you can store data files. By default they will not be web accessible. The directory is guaranteed to exist, and to be writable by the webserver user. For convenience, TWiki::Func::storeFile() and TWiki::Func::readFile() are provided to persistently store and retrieve simple data in this area.
 

Web Accessible Data

Line: 265 to 275
 
  • Use only alphanumeric characters, underscores, dashes and periods to avoid platform dependency issues and URL issues
  • Example: _Main_roundedge-ul.gif
Added:
>
>

Integrating with configure

Some TWiki extensions have setup requirements that are best integrated into configure rather than trying to use TWiki preferences variables. These extensions use Config.spec files to publish their configuration requirements.

Config.spec files are read during TWiki configuration. Once a Config.spec has defined a configuration item, it is available for edit through the standard configure interface. Config.spec files are stored in the 'plugin directory' e.g. lib/TWiki/Plugins/BathPlugin/Config.spec.

Structure of a Config.spec file

The Config.spec file for a plugin starts with the plugin announcing what it is: 
# ---+ BathPlugin
# This plugin senses the level of water in your bath, and ensures the plug
# is not removed while the water is still warm.
This is followed by one or more configuration items. Each configuration item has a type, a description and a default. For example: 
# **SELECT Plastic,Rubber,Metal**
# Select the plug type
$TWiki::cfg{BathPlugin}{PlugType} = 'Plastic';

# **NUMBER**
# Enter the chain length in cm
$TWiki::cfg{BathPlugin}{ChainLength} = '30';

# **BOOLEAN EXPERT**
# Turn this option off to disable the water temperature alarm
$TWiki::cfg{BathPlugin}{TempSensorEnabled} = '1';
The type (e.g. **SELECT** ) tells configure to how to prompt for the value. It also tells configure how to do some basic checking on the value you actually enter. All the comments between the type and the configuration item are taken as part of the description. The configuration item itself defines the default value for the configuration item. The above spec defines the configuration items $TWiki::cfg{BathPlugin}{PlugType}, $TWiki::cfg{BathPlugin}{ChainLength}, and $TWiki::cfg{BathPlugin}{TempSensorEnabled} for use in your plugin. For example, 
if( $TWiki::cfg{BathPlugin}{TempSensorEnabled} && $curTemperature > 50 ) {
    die "The bathwater is too hot for comfort";
}

The config.spec file is read by configure, and configure then writes LocalSite.cfg with the values chosen by the local site admin.

A range of types are available for use in Config.spec files:

BOOLEAN A true/false value, represented as a checkbox
COMMAND length A shell command
LANGUAGE A language (selected from {LocalesDir}
NUMBER A number
OCTAL An octal number
PASSWORD length A password (input is hidden)
PATH length A file path
PERL A perl structure, consisting of arrays and hashes
REGEX length A perl regular expression
SELECT choices Pick one of a range of choices
SELECTCLASS root Select a perl package (class)
STRING length A string
URL length A url
URLPATH length A relative URL path

All types can be followed by a comma-separated list of attributes.

EXPERT means this an expert option
M means the setting is mandatory (may not be empty)
H means the option is not visible in configure

See lib/TWiki.spec for many more examples.

Config.spec files are also used for other (non-plugin) extensions. in this case they are stored under the Contrib directory instead of the Plugins directory.

 

Maintaining Plugins

Line: 276 to 348
  The Plugin interface (TWikiFuncDotPm functions and handlers) evolve over time. TWiki 4.0 introduced new API functions to address the needs of Plugin authors. It also deprecated some functions. Some Plugins written for earlier TWiki releases using unofficial TWiki internal functions no longer work on the TWiki 4.0 codebase. All this means that some Plugins need to be updated to work on the TWiki 4.0 codebase.
Changed:
<
<		Organizations typically do not upgrade to the latest TWiki for many months. However, many administrators still would like to install the latest versions of a Plugin on their older TWiki installation. This need is fullfilled if Plugins are maintained in a compatible manner.
>
>		Organizations typically do not upgrade to the latest TWiki for many months. However, many administrators still would like to install the latest versions of a Plugin on their older TWiki installation. This need is fulfilled if Plugins are maintained in a compatible manner.
  TIP Tip: Plugins can be written to be compatible with older and newer TWiki releases. This can be done also for Plugins using unofficial TWiki internal functions of an earlier release that no longer work on the latest TWiki codebase. TWiki:TWiki.TWikiPluginsSupplement#MaintainPlugins has more.
Line: 300 to 372
  Related Topics: DeveloperDocumentationCategory, AdminDocumentationCategory, TWiki:TWiki.TWikiPluginsSupplement
Deleted:
<
<		-- Contributors: TWiki:Main.PeterThoeny, TWiki:Main.AndreaSterbini, TWiki:MainMikeMannix, TWiki:CrawfordCurrie
View topic | History: r34 < r33 < r32 < r31 | More topic actions...
 
This site is powered by the TWiki collaboration platformCopyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
Note: Please contribute updates to this topic on TWiki.org at TWiki:TWiki.TWikiPlugins