Lerking/pyxtend
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updated The birth of a python plugin architecture (markdown)

Lerking
2024-03-08 10:58:22 +01:00
parent e6638cd8c6
commit 10540dc153
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
The-birth-of-a-python-plugin-architecture.md
+3
@@ -21,11 +21,14 @@ My personal belief is that registration and activation should be kept separate.
- Activation should not be allowed unless the plugin is registered. - Activation should not be allowed unless the plugin is registered.
## Plugin requirements ## Plugin requirements
* Plugin manager to keep track of plugins and their statuses.
* 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 unregister (uninstall) * Plugin unregister (uninstall)
### Plugin manager
### Plugin registration ### Plugin registration
What should happen when a plugin registers? What should happen when a plugin registers?