On Tuesday, June 11, 2013 19:34:12 Marco Martin wrote:
On Tue, Jun 11, 2013 at 6:56 PM, Marco Martin notm...@gmail.com wrote:
On Tue, Jun 11, 2013 at 5:09 PM, Sebastian Kügler se...@kde.org wrote:
k. Not sure which is worse. I suppose, at least, that this
kind of porting can be done with a
On Wednesday, May 15, 2013 20:07:55 Marco Martin wrote:
On Tuesday 14 May 2013, Aaron J. Seigo wrote:
i think they should go
In a perfect world, yes. In the less perfect world we live in, it means
more porting work. Not sure which is worse. I suppose, at least, that this
kind of
On Tue, Jun 11, 2013 at 5:09 PM, Sebastian Kügler se...@kde.org wrote:
k. Not sure which is worse. I suppose, at least, that this
kind of porting can be done with a script.
i think the branch is pretty much ready to go now
Did you merge this one already?
no, not yet, didn't do any
On Tue, Jun 11, 2013 at 6:56 PM, Marco Martin notm...@gmail.com wrote:
On Tue, Jun 11, 2013 at 5:09 PM, Sebastian Kügler se...@kde.org wrote:
k. Not sure which is worse. I suppose, at least, that this
kind of porting can be done with a script.
i think the branch is pretty much ready to
On Tuesday 14 May 2013, Aaron J. Seigo wrote:
i think they should go
In a perfect world, yes. In the less perfect world we live in, it means
more porting work. Not sure which is worse. I suppose, at least, that this
kind of porting can be done with a script.
i think the branch is pretty
On Sunday, May 12, 2013 13:14:23 Marco Martin wrote:
plasma.topEdge (notice the lower case) that plasma object would be a
fugly :/ i'm not happy with the overly long PlasmaCore.Types.TopEdge, but i
guess that's the lesser of evils.
* Types name (or any other for what matters) is not
On Tuesday 14 May 2013 15:12:59 Aaron J. Seigo wrote:
On Sunday, May 12, 2013 13:14:23 Marco Martin wrote:
plasma.topEdge (notice the lower case) that plasma object would be a
fugly :/ i'm not happy with the overly long PlasmaCore.Types.TopEdge, but
i guess that's the lesser of evils.
On Tuesday 14 May 2013 17:53:18 you wrote:
In a perfect world, yes. In the less perfect world we live in, it means
more porting work. Not sure which is worse. I suppose, at least, that
this kind of porting can be done with a script.
unfortunately posting has to be dine anyways, since the
On Sunday 12 May 2013, Aaron J. Seigo wrote:
On Friday, May 10, 2013 19:44:09 Marco Martin wrote:
After many experiments in varuious failing directions, i have the branch
PlasmaTypesClass of palsma-framework
de-duplication is terrific.
it's still a draft state, i realize. the code in
On Friday, May 10, 2013 19:44:09 Marco Martin wrote:
After many experiments in varuious failing directions, i have the branch
PlasmaTypesClass of palsma-framework
de-duplication is terrific.
it's still a draft state, i realize. the code in plasma.h is inconsistent in a
few ways (e.g.
Hi all,
After many experiments in varuious failing directions, i have the branch
PlasmaTypesClass of palsma-framework
The problem:
we need a way to expose the enums used in libplasma such as FormFactor,
Location, Constraints etc in some way accessible to QML, for applet bindings,
and any
The cons don't seem very problematic, any other reasons why you don't like
the approach? I guess the only other thing you can do is use strings, and
that would suck even more :P
On Fri, May 10, 2013 at 11:14 PM, Marco Martin notm...@gmail.com wrote:
Hi all,
After many experiments in varuious
12 matches
Mail list logo
