Cursorsors: where?

[Jens Reuterberg]

Yes you did. 

But like I said then - what options do we have? 
a) Get C++ programmers
b) Ship the frankensteins monster of visual design

Now I am not technically adept enough to know what a "c)" could be in this 
case but I refuse to accept that there isn't one. But lets bone this out 
again, the main issue with the Oxygen window decoration isnt so much shading 
and other details but it's the buttons. If we can temporarily change those we 
could get a long way away from the problem and buy ourselves time to fix it 
properly.

Can we? Anyone who knows whether that is possible or will cause ten thousand 
issues along the line?

/Jens

On Thursday 24 April 2014 10.06.15 Martin Gräßlin wrote:
> On Thursday 24 April 2014 09:38:20 Jens Reuterberg wrote:
> > On Thursday 24 April 2014 07.28.28 Martin Gräßlin wrote:
> > > On Wednesday 23 April 2014 23:10:41 Thomas Pfeiffer wrote:
> > > > On Wednesday 23 April 2014 13:58:02 Martin Gräßlin wrote:
> > > > > On Wednesday 23 April 2014 13:53:56 David Edmundson wrote:
> > > > > > Right now we have an oxygen repo full of all different things
> > > > > > (icons,
> > > > > > window decoration, qstyle)
> > > > > > 
> > > > > > We can make a Breeze repo full of all these new different things.
> > > > > 
> > > > > I think that's the best approach to it. We will hopefully soon see
> > > > > stuff
> > > > > like window decoration and widget style and so on. Let's move it
> > > > > together
> > > > > like with Oxygen.
> > > > 
> > > > Currently, both a widget theme and a windeco are in the making.
> > > > However, neither of them are C++ at the moment. There is a quite well-
> > > > progressing QtQuickControls style, as well as an accompanying QtCurve
> > > > preset, and several quite nice windeco themes (currently
> > > > Aurorae-based).
> > > > All of them still need polishing, though.
> > > > So the next step after the design is done would be to make a C++
> > > > widget
> > > > theme based on the design of the QtQuickControls style, and after the
> > > > Plasma team has decided which windeco should be the default, a C++
> > > > windeco
> > > > based on that, right?
> > > 
> > > At least for windeco we will need a C++ implementation as Aurorae is not
> > > suited as a default component.
> > > 
> > > Cheers
> > > Martin
> > 
> > Which of course leaves us in the same predicament as last time - where do
> > we find C++ programmers to finish this?
> 
> we will need to find the C++ programmers, Aurorae is unsuited as a default.
> I rather ship something which doesn't look good, than reading a million
> times how slow Plasma Next is. The rendering of the window decoration is
> very expensive and with the Qt 5 transition it unfortunately became worse
> for Aurorae.
> 
> Yes it can mean lost chances for the design, but shipping an Aurorae theme
> as default would also mean lost chances in the not repeating 4.0 mistakes.
> We are caught between a rock and a hard place, here.
> 
> I can only repeat that performance was never a design goal of Aurorae and
> from the first day when I started working on it, it was obvious to me that
> Aurorae shall never be used for a default decoration. I'm quite certain I
> pointed that out before work started on the Aurorae theme ;-)
> 
> Cheers
> Martin