Re: Proposal: make libplasmaquick semi-privare

2014-02-20 Thread Marco Martin
On Thursday 20 February 2014 12:45:15 David Edmundson wrote: > Can I request moving SVG and FrameSVG into PlasmaQuickPrivate -1 > 1) I need to tweak the API to get rid of the paint() methods and > instead add render hints to the pixmap() method > > 2) I want to destroy most of FrameSVG :) > > 3

Re: Re: Proposal: make libplasmaquick semi-privare

2014-02-20 Thread Martin Gräßlin
On Thursday 20 February 2014 12:45:15 David Edmundson wrote: > Can I request moving SVG and FrameSVG into PlasmaQuickPrivate > > 1) I need to tweak the API to get rid of the paint() methods and > instead add render hints to the pixmap() method > > 2) I want to destroy most of FrameSVG :) this wo

Re: Proposal: make libplasmaquick semi-privare

2014-02-20 Thread David Edmundson
Can I request moving SVG and FrameSVG into PlasmaQuickPrivate 1) I need to tweak the API to get rid of the paint() methods and instead add render hints to the pixmap() method 2) I want to destroy most of FrameSVG :) 3) I want to put in an implicit sharing of QSGTextures, exposed via Plasma::SVG

Re: Proposal: make libplasmaquick semi-privare

2014-02-17 Thread Giorgos Tsiapaliokas
On 02/14/2014 06:49 PM, Sebastian Kügler wrote: On Friday, February 14, 2014 16:38:29 Marco Martin wrote: I would like for now to *not* install headers for libplasmaquick for now, So that would mean the systray has a copy of a header? Maybe in order to avoid making copies of the headers we

Re: Proposal: make libplasmaquick semi-privare

2014-02-14 Thread Sebastian Kügler
On Friday, February 14, 2014 16:38:29 Marco Martin wrote: > I want to propose the following for the first plasma-next release (actually > for the first frameworks release with plasma-framework in it) > right now plasma-framework provides two libraries: libplasma that is purely > logic-only, no qm

Re: Proposal: make libplasmaquick semi-privare

2014-02-14 Thread David Edmundson
Oh, and we definitely need a few of these to compile workspace. dataengine.h especially. I withdraw my comment ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel

Re: Proposal: make libplasmaquick semi-privare

2014-02-14 Thread Sebastian Kügler
On Friday, February 14, 2014 16:57:12 David Edmundson wrote: > If we do that is there any point in releasing libplasma headers? Possibly less so for Applet and the likes, but I definitely see Plasma::Package and Plasma::Theme being useful. So yes. :) -- sebas http://www.kde.org | http://vizZzi

Re: Proposal: make libplasmaquick semi-privare

2014-02-14 Thread David Edmundson
Fine with me. If we do that is there any point in releasing libplasma headers? It's practically impossible to do anything useful with them without libplasmaquick. It's not like anyone can subclass the Applet class in their applet. It will mean we don't have to be API stable on them. David __