On Wednesday, October 5, 2011 12:49:58 Ivan ÄukiÄ wrote:
> > i really recommend KDBusService.
>
> Ok, so that means this will be a brang of kamd for kf5?
no, i don't think we need that. for now we can copy that one class into a
frameworks/ folder and then when we port this to f5, we can git rid
> i really recommend KDBusService.
Ok, so that means this will be a brang of kamd for kf5?
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
On Tuesday, October 4, 2011 18:29:33 Ivan Cukic wrote:
> General question - do you want to create a fw5 branch or something like
> that?
>
> Aaron
>
> > KUniqueApplication: this lives in kdeui ... just to provide a way to
> > have only one instance of the app. ugh. in Frameworks there is libkdbus
On Tuesday 04 October 2011 18:29:33 Ivan Cukic wrote:
> Do we even need KDBusService? Just a check of
> QDBusConnectionInterface::isServiceRegistered can be used for this.
Well, you need to add the fact that you also have to verify the connection to
the bus to trigger it if necessary, register the
> Given the low interest of other window managers to collaborate recently,
> I doubt that. But do we care, if not?
I don't know really. Sometimes I want to say "hey, this is a hard dep,
deal with it", but then I see people who use rather quirky setups.
But, yeah, we can do it kwin only, and if
On Tuesday 04 October 2011 18:29:33 Ivan Cukic wrote:
> General question - do you want to create a fw5 branch or something like
> that?
>
> Aaron
> > KUniqueApplication: this lives in kdeui ... just to provide a way to
> > have only one instance of the app. ugh. in Frameworks there is libkdbus
>
General question - do you want to create a fw5 branch or something like
that?
Aaron
> KUniqueApplication: this lives in kdeui ... just to provide a way to
> have only one instance of the app. ugh. in Frameworks there is libkdbus
> which has a KDBusService which provides the same capabilities. por
On Tuesday 04 October 2011 16:33:03 Aaron J. Seigo wrote:
> hi all...
>
> i experimented a bit this morning with cutting the fat from
> kactivitymanagerd.
> in particular i focussed on the following.
>
> KUniqueApplication: this lives in kdeui ... just to provide a way to have
> only
> one in
hi all...
i experimented a bit this morning with cutting the fat from kactivitymanagerd.
in particular i focussed on the following.
KUniqueApplication: this lives in kdeui ... just to provide a way to have only
one instance of the app. ugh. in Frameworks there is libkdbus which has a
KDBusServ
