easy plugin architecture

Registered by pierrelux on 2010-03-23

Functionnalities will mostly come through plugins so it must be easy to develop, install, activate, configure, access the plugins.

Blueprint information

Status:
Started
Approver:
Philippe April
Priority:
High
Drafter:
gbastien
Direction:
Needs approval
Assignee:
gbastien
Definition:
Approved
Series goal:
Accepted for trunk
Implementation:
Beta Available
Milestone target:
milestone icon 0.1.0-alpha
Started by
gbastien on 2010-04-08

Related branches

Sprints

Whiteboard

Develop: Have good documentation on how to develop plugin and decide what/where/how hooks should be implemented and document those in the AuthPuppy API wiki. WIKI IS CONSISTENT WITH CODE

Install: The plugin management interface should list all available plugins from a given source with their latest version. Clicking them should download them and make them available to activation. DONE

Activate: plugin management interface with checkboxes to enable/disable DONE

Configure: Clicking the plugin name in the plugin management system should bring up the interface to configure the plugin (if configuration is necessary of course) DONE

Update: If a new version of the plugin is available, it should be possible to easily download the new code and migrate the database if necessary. DONE

Access: If the plugin provides new menu options, then these should appear in the menu and the user access it if he has the privileges. DONE

Use: Plugins should be able to hook at different points (events?) in the execution of the page. Those hook points should be documented with the details of the values that are passed to it. DONE

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.