Ticket #68 (closed defect: fixed)
Move the plugin code to its own class
| Reported by: | tsee | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | editor | Version: | |
| Keywords: | Cc: |
Description
In the wake of adding the plugin-from-PAR functionality, it struck me that the plugin code (which can only grow) should really be in its own class.
Hence, I propose the Padre::PluginManager? class (not Padre::Plugin::Manager for a reason).
The attached patch implements the move and does some cleanup at the same time. Unfortunately, this relies on ticket #66 (PAR support) and #67 (autocompletion) since I made the change to my modified checkout. Sorry.
The attached patch includes those of #66 and #67 as well. I don't think it's separable from #66, but I'll happily produce a patch without the changes in #67 on demand.
This change should make it easier to move the plugin-loading to the time *after* the window has been opened. It's only a single method call. (see ticket #1)
Attachments
Change History
Changed 5 years ago by tsee
- Attachment ticket_66_67_68.diff added
Patch implementing this ticket, as well as 66/67