A proposed structure for plugins

Registered by Mohammad AbuShady on 2011-05-24

I've seen the plugins that are written here and i would like to propose a new way to write plugins, I think there should be a main class that defines the plugins, it would be just an abstract, defining the function names and the properties that each plugin should have, then each plugin define should extend this abstract class and pass some parameters to it while constructing, these parameters would define every thing needed about these plugins ( for example : files needed to be backed up and their paths, program name, the program's executable file, etc ).
after creating the plugin instance we could call the pre defined functions that exist in the parent class, this should ease the creation of plugins, and also the maintenance in case of some major change that needs to be applied on all plugins at the same time, since we will only change the parent class, and every thing will reflect on the plugin instances..

Blueprint information

Status:
Not started
Approver:
Duane Hinnen
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
Mohammad AbuShady
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.