[dokuwiki] Re: Plugins

[Andreas Gohr <andi@xxxxxxxxxxxxxx>]

On Thu, 4 Aug 2005 10:04:23 +0100
"Chris Smith" <chris@xxxxxxxxxxxxx> wrote:

> Recently some person(s) have mentioned dokuwiki should do everything
> by plugins, I have asked for template plugins :-) and Andi has said
> there is a real need for action plugins.
> 
> I'd like to a couple of questions to more fully understand what is
> meant.
> 
> Am I right in thinking doing everything via plugins would require a
> large amount of code refactoring and although its a neat idea, it is
> something that if it did happen, would happen very gradually?

I agree but I'm not sure if it would have any benefits at all. A wiki should 
come with some sane default syntax anyway so we would have to include all these 
to-be-created plugins by default. It would mean to have to load multiple files 
instead of just the few ones used currently which would create some overhead 
(though not too much I guess). So moving everything to plugins sounds good but 
has no real advantage in the end. I guess our resources are better spend on 
other things.

> When I think of actions, I think of the things dokuwiki does -
> showpage, edit, old revisions, index, search, etc.  Someone else has
> mentioned something more like triggers on more basic functions, on
> create new page, on adding a new user (see bugs>409).  Can Andi or
> anyone explain their ideas on this?

That's exactly what I meant by action plugins. Having defined entry points 
which plugins can use to manipulate the way DokuWiki behaves. Eg. I imagine 
something like an onPageSave trigger which gives the whole text to save to the 
registered plugin which then can manipulate the text before it is returned to 
DokuWiki's control which then does the saving.

There would be some way of event registering needed to avoid needing to call 
each plugin on each trigger.

There were some discussions on how this whole thing should work (eg. on 
http://wiki.splitbrain.org/wiki:discussion:pluginapi_ideas) but AFAIK no real 
code was written yet.

> I mentioned yesterday, I have been tinkering with a plugin manager. 
> That could well fit in as an "admin function" plugin.  Right now there
> is only one admin function, Page ACL, any code refactoring to make an
> admin plugin interface "may" be quite straight forward, with an
> interface like:- plugin info
> - menu option to add to admin page (multilingual?)
> - sort order for menu option
> - method called when user chooses menu option

Such an admin plugin system sound's reasonable to me. This way 
syntax/action/whatever plugins could come with their own administration as well.

> I wouldn't like to tackle an action plugin interface, though I would
> be prepared to help out if someone else took the lead.  But I think I
> could sort out an interface for admin function plugins if it was
> desired.

I'm open for any suggestions and code as always ;-)

Andi

• Follow-Ups:
  • [dokuwiki] Re: Plugins
    • From: Chris Smith

• References:
  • [dokuwiki] alphabetical order
    • From: Adam Kosmin
  • [dokuwiki] Plugins
    • From: Chris Smith

Other related posts:

[dokuwiki] Plugins

[dokuwiki] Re: Plugins

[dokuwiki] Re: Plugins

[dokuwiki] Re: Plugins

[dokuwiki] Re: Plugins

[dokuwiki] Re: Plugins

[dokuwiki] Re: Plugins