Updated The birth of a python plugin architecture (markdown)
@@ -10,8 +10,23 @@ A. The plugin architecture design pattern (also known as microkernel) is a philo
|
|||||||
|
|
||||||
Q. What is required of a plugin system?
|
Q. What is required of a plugin system?
|
||||||
|
|
||||||
|
A. These elements must be in place for a basic plugin system.
|
||||||
|
- A core system which handles registration/unregistering
|
||||||
|
- Some sort of configuration file with info about registered plugins. This could be any type of file for storing basic data i.e. json, xml, yaml etc.
|
||||||
|
- Plugins using the plugin class as its main component. This ensures interface stability.
|
||||||
|
|
||||||
|
|
||||||
## Plugin requirements
|
## Plugin requirements
|
||||||
* Plugin registration (installation)
|
* Plugin registration (installation)
|
||||||
* Plugin activation (activate the plugin)
|
* Plugin activation (activate the plugin)
|
||||||
* Plugin deactivation (deactivate the plugin)
|
* Plugin deactivation (deactivate the plugin)
|
||||||
* Plugin un-registration (un-installation)
|
* Plugin unregister (uninstall)
|
||||||
|
|
||||||
|
### Plugin registration
|
||||||
|
What should happen when a plugin registers?
|
||||||
|
|
||||||
|
### Plugin activation
|
||||||
|
|
||||||
|
### Plugin deactivation
|
||||||
|
|
||||||
|
### Plugin un-registering
|
||||||
Reference in New Issue
Block a user