<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 06/17/2014 10:56 AM, Marco Martin
wrote:<br>
</div>
<blockquote
cite="mid:CAD6_Bot5oCeu2D7Gyejx-cHqvcKsAE2G0+StPKhpMTL9J=352Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Thu, May 29, 2014 at 3:09 PM,
Marco Martin <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:notmart@gmail.com" target="_blank">notmart@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">On Thursday 15 May 2014 11:39:00 Jens
Reuterberg wrote:<br>
</div>
<div class="">> Ok so after the feedback from the Beta
Release an issue that we knew was<br>
> coming have happened. Visuals being the most easily
accessible bit of<br>
> anything technical, people have reacted negatively
to the lack of change.<br>
<br>
</div>
just to give a shot on every and single options, i gave a
try to modifying<br>
oxygen in order to make it look like breeze (therefore
sharing all the things<br>
that it does that are not related to painting, like drag
the window from<br>
anywhere)<br>
this is the half done, half missing attempt (ignore the
non changed elements)<br>
<a moz-do-not-send="true"
href="http://wstaw.org/m/2014/05/29/plasma-desktophP1414.png"
target="_blank">http://wstaw.org/m/2014/05/29/plasma-desktophP1414.png</a><br>
<br>
is pretty hacky, but *maybe* is possible to have in the
end only a different<br>
stylehelper (and pixelmetrics/stylehints)<br>
so could be something worth exploring in the future<br>
<br>
</blockquote>
<div>Adding Hugo with a very due explanation of what it is:</div>
<div>The Visual Design Group came up with an idea for a new
design for a widget style in KDE.</div>
<div>But of course a Qt widget style is an huge undertaking
that will take a lot to do.</div>
<div>Now, Oxygen is the sum of years of experience and
fixes, (and also does a ton of things to make application
behave well that are beside just "painting", not to
mention the companion themes that integrate nicely gtk 2
and 3 apps) and would really be a shame to lose all those
years of development and experience, so I was wondering
how hard would be to adapt the Oxygen codebase to a new
visual style (would be a new style, or perhaps hopefully
something sharing a lot of code)</div>
<div><br>
</div>
<div>in the link above, there is a screenshot of an
attemptIi made to quick and dirty try to adapt some of the
elements (is incomplete and only partial, but promising,
seems that changing rounded radiuses and removing some
gradients here and there gets pretty close)</div>
<div><br>
</div>
<div>Hugo, do you think it would be a feasible thing? And
would you be interested in it? (I was thinking about
something like maintaining most of the style, and set
apart an oxygenhelper(as is now) vs breezehelper for the
different visual related things)</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Marco Martin</div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
Hi Marco, others,<br>
<br>
Sorry for the delayed answer.<br>
<br>
First off, I unfortunately have very little time left since about
half a year to dedicate to KDE/Oxygen aside from bug fixing and it
is likely not going to improve. So that I would not be a reliable
choice for undertaking the development of a Breeze Qt4/Qt5/Gtk2/Gtk3
widget theme. (though I could give an occasional hand to anyone
volunteering). <br>
<br>
As for starting from Oxygen's code base, I think it is a good idea
indeed. Large amount of code could likely be reused quite unchanged:
animations, window grabbing, fancy splitters. They could even be
moved to a library, that Breeze would load. <br>
(ok there is versionning, API freeze etc. involved, but no serious
core development)<br>
<br>
As for the styling, indeed rewriting the helper class is a possible
start. Also, current oxygen has basically one method for every
primitive/control/etc. So it should also be easy to just inherit
from it, and just re-implement these methods one after the other ...
<br>
<br>
Still, that would not bring you Gtk2 and Gtk3, which is quite a
serious issue. <br>
<br>
For such things, QtCurve is indeed a good candidate, since as far as
I know it is the only widget theme around that implements all major
flavors of toolkits ... but has an issue of "over-configuraribility"
by design, which is not so good for branding, imho.<br>
<br>
Last but not least, you could try "hire" the latest QtCurve dev for
KDE (Yichao Yu <a class="moz-txt-link-rfc2396E" href="mailto:yyc1992@gmail.com"><yyc1992@gmail.com></a>)<br>
, to work on a cut-down and cleaned-up version of QtCurve, called
Breeze. The guy is good, nice, very active and knows all of both Qt
and Gtk. He has help debugging/fixing oxygen and qtcurve
simultaneously quite a number of times already. <br>
<br>
QtCurve already use (copy) part of oxygen's code (and vice versa),
so here also I could contribute, without taking maintainership.<br>
<br>
... and finaly, there is window decoration. I guess one could start
with an aurorae theme (although not optimal, since you ultimately
need some extra features, such as synching with the widget theme,
for background gradient for instance).<br>
<br>
Hugo<br>
<br>
<br>
</body>
</html>