On Monday, July 01, 2013 14:35:51 Kevin Krammer wrote:
> > Well, the goal, for me, is to make plugin factories work. Right now, we
> > only have a handful constructor, and I want to make it possible to build
> > those with as little extra hassle as possible -- it means porting all
> > plugins, and
On Monday, 2013-07-01, Sebastian Kügler wrote:
> On Monday, July 01, 2013 13:35:27 Kevin Krammer wrote:
> > On Monday, 2013-07-01, Sebastian Kügler wrote:
> > > On Monday, July 01, 2013 09:03:29 Kevin Krammer wrote:
> > > > What if the macro only creates the header content (as its name
> > > > alre
On Monday, July 01, 2013 13:35:27 Kevin Krammer wrote:
> On Monday, 2013-07-01, Sebastian Kügler wrote:
> > On Monday, July 01, 2013 09:03:29 Kevin Krammer wrote:
> > > What if the macro only creates the header content (as its name already
> > > suggests)?
> > >
> > > name::create() could then be i
On Monday, 2013-07-01, Sebastian Kügler wrote:
> On Monday, July 01, 2013 09:03:29 Kevin Krammer wrote:
> > What if the macro only creates the header content (as its name already
> > suggests)?
> >
> > name::create() could then be implemented in a plugin specific way, not
> > requiring a certain
On Monday, July 01, 2013 09:03:29 Kevin Krammer wrote:
> On Monday, 2013-07-01, Sebastian Kügler wrote:
> > Open questions:
> >
> >
> > - KPart and QWidget create* calls: In my current patch, these are simply
> >
> > ignored.
> > I'm getting away with one overridden function in our
> > macro
On Monday, 2013-07-01, Sebastian Kügler wrote:
> Open questions:
>
> - KPart and QWidget create* calls: In my current patch, these are simply
> ignored.
> I'm getting away with one overridden function in our
> macro-generated KPluginFactory subclass, it all seems to boil down to
>
>
Hi,
On Tuesday, June 25, 2013 15:04:52 Sebastian Kügler wrote:
> I'll have to let the rest of your email sink in a bit, and then play around
> with it.
I think I've roughly figured it out, see attached patch.
It registers KPluginFactory as Q_INTERFACE and provides a macro that writes
out a sim
Hi David,
On Tuesday, June 25, 2013 12:39:08 David Faure wrote:
> > Ignoring our home-made deprecation warning, it seems KPlugin* is still
> > working.
>
> Clearly I did too good a job with the hack in the macro. It works so people
> want to keep that hack
>
> The problem is that it again creat
Le lundi 24 juin 2013 12:48:55 Sebastian Kügler a écrit :
> Hey,
>
> As you know, I'm looking into what's needed for proper plugin support in
> KF5, trying to understand what's going on, and at least making our KDE4
> solution work for KF5. Qt's native plugin functionality is clearly lacking
> for
Hey,
As you know, I'm looking into what's needed for proper plugin support in KF5,
trying to understand what's going on, and at least making our KDE4 solution
work for KF5. Qt's native plugin functionality is clearly lacking for our
usecase, as it doesn't allow to have multiple instances of the
10 matches
Mail list logo
