On 27 Aug 2012, at 14:29, Mark <mark...@gmail.com> wrote:
> On Mon, Aug 27, 2012 at 12:41 PM, Stuart Dallas <stu...@3ft9.com> wrote:
>> On 26 Aug 2012, at 19:42, Mark <mark...@gmail.com> wrote:
>>> 2. Let the plugin itself (so in this case PluginOne.php) open itself
>>> and register it to the PluginLoader.
>>> With the first option i have to do eval which i try to avoid if possible.
>>> With the second solution the PluginLoader probably has to be a singlethon.
>> Why does it need to be a singleton?
> Well, i would then do something like this from within the included
> plugin file after the class:
> PluginLoader::getInstance()->registerPlugin(new PluginOne());
> Or something alike.
I'm not sure I see what PluginLoader is doing? It makes more sense to me if you
register like so:
Then you get an instance of the plugin:
$plugin = PluginLoader::getInstance()->factory('PluginOne');
Tho, even then I don't see what the PluginLoader is adding to the party.
> Thank you for your advice, really appreciated.
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php