Tags:
create new tag
, view all tags
Some Plugins may have a dependence on another Plugin:
  • other plugin might be required for it to work
  • might give enhanced functionality e.g. the presence of the SessionPlugin gives extra capability to the TigerSkinPlugin.pm

How should dependency be:

  • implemented
  • documented

At present implementation could be:

  • Check for presence of Plugin topic - not a guarantee that the plugin is actually present
  • Check for presence of Plugin .pm file

Alternatively an array of enabled plugins could be supplied or a query written that indicates if a certain plugin is present. Would this be worth having?

Dependencies should be documented in the relavent section in the Plugins Web.

A plugin should fail initialisation and call writeWarning if a necesary dependency is missing.

-- JohnTalintyre - 30 Jul 2001

This strikes me as being useful, but in the interests of gettting the TWikiSpring2001 out soon, it might be best just to document the dependencies in the plugin pages, and leave any code changes till later.

-- RichardDonkin - 01 Aug 2001

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r3 - 2001-09-18 - MikeMannix
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.