2012/8/31 Kevin Ottens :
> Now if that was a case of "the framework can't work without the dependency"
> I'd have a position similar to your. But here it's depending on the nature of
> the plugins, not on what the framework itself needs, that's what rings the
> "worth doing it" to me.
I understand
On Friday 31 August 2012 18:26:24 Dario Freddi wrote:
> 2012/8/31 Kevin Ottens :
> > On Wednesday 29 August 2012 23:53:32 David Faure wrote:
> >> Solution 1b: move KPluginLoader to kservice, but solve the i18n
> >> dependency by having some singleton inside KPluginLoader emit a signal
> >> when loa
2012/8/31 Kevin Ottens :
> Hello,
>
> On Wednesday 29 August 2012 23:53:32 David Faure wrote:
>> KService, KServiceTypeTrader and KMimeTypeTrader (all of which I moved to a
>> new "kservice" framework), all have a template method (createInstance*)
>> which uses KPluginLoader to load the plugin desc
Hello,
On Wednesday 29 August 2012 23:53:32 David Faure wrote:
> KService, KServiceTypeTrader and KMimeTypeTrader (all of which I moved to a
> new "kservice" framework), all have a template method (createInstance*)
> which uses KPluginLoader to load the plugin described by the given service,
> or
