On Friday 15 July 2011, Aaron J. Seigo wrote:
>
> anyways.. the thing i'm contemplating is this:
>
> Removing all the "load(..)" methods from the classes, and instead have
> everything use PluginManager directly.
+1
> pros:
> * fewer methods in general in the API, particularly ones that plugi
Hi+1, that all makes sense to me, and sounds like a Good Thing.R--Ryan Rix http://rix.Sihttp://opensource.com : Where Open Source multipliesOn Jul 15, 2011 4:27, Aaron J. Seigo wrote: hi...
so, we have the PluginLoader class now which is there to allow extending the
loading of plugins by the app
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/101943/#review4741
---
The code from the SoK project is now in an own branch:
https://
On Friday, July 15, 2011 13:26:45 Aaron J. Seigo wrote:
> thoughts?
Having used this kind of API in Plasma a few times, I'd say the using
PluginLoader directly would not be a huge burden. I wouldn't mind this change.
--
sebas
http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
hi...
so, we have the PluginLoader class now which is there to allow extending the
loading of plugins by the application.
there are methods like: PluginLoader::loadApplet and PluginLoader::loadPackage
these are generally only used by the internals of classes like Applet::load,
which is current
