I agree with Marco,
Just would like to remark that building the styles for qtquickcontrols
should be top priority.
2013/8/19 Marco Martin
> On Monday 19 August 2013, Aaron J. Seigo wrote:
> > no matter how wonderful it is to have a single shared implementation
> > upstream so we don’t have to
On Monday 19 August 2013, Aaron J. Seigo wrote:
> no matter how wonderful it is to have a single shared implementation
> upstream so we don’t have to do anything but implement applications, we
> have to hit the three points above.
>
> in the end API, stability and device spectrum are what matters
On Monday, August 19, 2013 01:05:50 David Edmundson wrote:
> After discussions with a few people, I decided for an experiment to port
> PlasmaComponents Button to use QtQuickControls [1] internally but use the
> styles API [2] to make it look like the original PlasmaComponents button.
the things s
Right, that's basically what I had in mind when I said I can split things
into the style files.
The key thing I was trying to stress is that we don't need to implement a
whole style before we can start using it from some PlasmaComponents to get
benefits and that we don't need to port all the plasm
On Monday 19 August 2013, Eike Hein wrote:
> On Monday 19 August 2013 11:55:14 Marco Martin wrote:
> > for being able to do a decent desktop application (or even just the
> > settings dialogs) some things are still needed, in part feature missing,
> > in part making it play well with oxygen (and ox
On Monday 19 August 2013 11:55:14 Marco Martin wrote:
> for being able to do a decent desktop application (or even just the settings
> dialogs) some things are still needed, in part feature missing, in part
> making it play well with oxygen (and oxygen play well with them) since it's
> a qstyle inf
On Monday 19 August 2013, David Edmundson wrote:
> > If this will be how we proceed, it shouldn't be done inline, but as a
> > standalone style together the others.
>
> So there's 3 proposals being talked about here:
> - We keep Plasma Components as is
> - We create a proper QtQuick Controls sty
On Mon, Aug 19, 2013 at 10:55 AM, Marco Martin wrote:
> On Monday 19 August 2013, David Edmundson wrote:
> > After discussions with a few people, I decided for an experiment to port
> > PlasmaComponents Button to use QtQuickControls [1] internally but use the
> > styles API [2] to make it look li
On Monday 19 August 2013, David Edmundson wrote:
> After discussions with a few people, I decided for an experiment to port
> PlasmaComponents Button to use QtQuickControls [1] internally but use the
> styles API [2] to make it look like the original PlasmaComponents button.
>
> This is pushed in
On Monday 19 August 2013 01:05:50 David Edmundson wrote:
> I think given the current API changes it makes sense to use this
> opportunity to make this change. I believe we will get better more stable
> code for it. I can do most the changes.
I'm with you on this, and I'm really relieved it turned
On Mon, Aug 19, 2013 at 2:05 AM, David Edmundson wrote:
> After discussions with a few people, I decided for an experiment to port
> PlasmaComponents Button to use QtQuickControls [1] internally but use the
> styles API [2] to make it look like the original PlasmaComponents button.
>
> This is pu
After discussions with a few people, I decided for an experiment to port
PlasmaComponents Button to use QtQuickControls [1] internally but use the
styles API [2] to make it look like the original PlasmaComponents button.
This is pushed in the plasma-frameworks branch davidedmundson/controls
Advan
12 matches
Mail list logo
