Widget and windeco themes for Plasma Next

[Andrew Lake]

I think it was already discussed and mutually decided that the path forward
is to continue using Oxygen as default widget and windeco for at least the
first Plasma Next release. The VDG work in these areas will be optional at
best so that we can get some real world validation before making them
default.

During that validation period the windeco theme will be QML which will be
ported to C++ in order that it can be used as the default somewhere down
the line.

For the widget theme, we will continue to use the QTCurve settings to
support QStyle based apps in the short term. If a C++ solution becomes
viable, yay, but I'm personally not putting much effort into it. The
QtQuick Controls style will continue to be the reference UI controls style
for the visual design and we will refine it during the validation period
(already have some work to do). Regarding the plasma widget theme, just let
us know the medium terms plans for how the QtQuick controls style will be
used and we'll adjust as necessary.

The plan all along, at least as far as I understood it, has been to slowly
phase this stuff in, over several releases if necessary, as we become
confident in their use for the default. I think that's the best plan and we
should stick to it.

Hope this helps,
Andrew Lake
On Apr 24, 2014 6:05 AM, "Marco Martin" <notmart at gmail.com> wrote:

> On Thursday 24 April 2014 14:11:57 Thomas Pfeiffer wrote:
> > === Where do we go from here? ===
> >
> > If we ship what we have now, we'll have Breeze and Bridge together with
> > Oxygen widget and windeco theme.
> > While this has the advantage that Oxygen is "tried and true", it has the
> > following drawbacks:
> > - The Oxygen QtQuickControls style in its current condition (at least
> > from any Plasma Next screenshots and videos I've seen) looks unpolished
> > as hell. Labels in buttons aren't aligned correctly and there are other
> > problems as well. If we ship Plasma Next like this, everything looks
> > beautiful... until someone opens a GUI which was made with
> > QML/QtQuickControls (which is all of Plasma's own GUIs iirc). As soon as
> > people do, what they get looks like a crappy version of Plasma Current
> > (aka "KDE 4").
> > I don't think we want this. So if we want to at least be visually on par
> > with current Plasma, additional work would have to go into the Oxygen
> > QtQuickControls style (and according to David, a bug in Qt would have to
> > be fixed)
>
>
> As i made clear many times already, I am all for still defaulting to Oxygen
> for the first release (and possibly the second, for what matters)
> A QStyle is years of working around corner cases, and there is no way
> around
> that.
>
> Also, we are already battling against so many regressions that a strong
> discontinuity as a different default qstyle is the last thing needed
> (especially when realistically, most applications will be KDE4 ones for a
> long
> time still)
>
>
> It's true that doesn't go much together with the breeze plasma theme, but
> they
> always were distinct, so is not really a big of an issue (i did the first
> mockups of breeze explicitly to go together with oxygen in fact, since i
> always assumed it was what it was going to be used in the first release)
>
> Now, using QtCurve would be the less of the evils compared to go altogether
> with a new theme (but an evil still, the fact that i don't think any good
> look
> can come out of it is at least subjective ;)
>
> In the end the less subjective reasons i have for this, is that i really
> think
> if we want to have any remote possibility of success in the first release
> the
> top priorities should be maximum continuity and minimize the potential
> sources
> of regressions (and since a qstyle affects just everything, do your math)
> and
> everything else has to take the backseat (yes, even unity of style)
>
> So, I think changing away from Oxygen would be an huge mistake (saying
> again,
> just for the record).
> If everybody wants to do that fine, but whatever it replaces it, *must*
> have a
> qt4 and a gtk version (iirc qtcurve does have gtk?), because integration
> with
> KDE4 and GTK apps is way more important than with the workspace, that was
> deemed to be different in the first place.
>
>
> Cheers,
> Marco Martin
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel at kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20140424/7084dcc4/attachment.html>