Move the plugin code to its own class
|Reported by:||tsee||Owned by:|
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.
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)