<div class="gmail_quote">Hi,<br><br>2012/6/4 Marco Martin <span dir="ltr"><<a href="mailto:notmart@gmail.com" target="_blank">notmart@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Monday 04 June 2012, Ivan Čukić wrote:<br>
> Hi all,<br>
><br>
> With qml-ifying plasma, we have the opportunity to completely break<br>
> the current theming system and make something that would work. I'm<br>
<br>
</div>well, not really, since svg and framesvg are directly binded to qml (and quite<br>
heavily used, even outside of components) so current qml stuff already has a<br>
pretty heavy dependence on it, at least the api part of it (would be possible<br>
to maintain 100% compatibility of current qml code if the api of framesvgitem<br>
is kept even using a different backend).<br></blockquote><div><br>Maintaining compatibility with SVG wouldn't be hard.<br>It would be needed a QML Style that could handle SVGs as Themes.<br> <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="im"><br>
> usually all for back-compatibility, but in this case I think we should<br>
> start from scratch. We have already had discussions about why the<br>
> current theming system is not sufficient, so I'm not going to repeat<br>
> them.<br>
><br>
> With the plans [1] for QML themes, we'll get a proper theming for<br>
> Plasma widgets, the thing that will remain is to do the same for<br>
> applets, panels and similar.<br>
<br>
</div>desktop widgets will have (at least i hope) be painted with qstyle, for<br>
retrocompatibility, is still not really clear what are the plans for something<br></blockquote><div> </div><div>Exactly, the QStyle painting will be there for retro compatibility and implementing<br>
new styles with QML are possible, but the goal is opening doors for Styles <br>written in QML or C++ QtQuick.<br> <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
different from qstyle, that post seems still deep in the investigative phase<br>
(Daker, any news/updates about that?)<br></blockquote><div><br>It's important to notice that currently it's a separated project from Qt Desktop Components.<br>Our intention is to join both efforts and this will be under discussion at QtCS.<br>
I hope that something good comes out from it.<br> <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
as i said, my main concern is that framesvg is used a lot around in qml, so<br>
that would require again a new porting effort.<br></blockquote><div><br>In the proposed architecture [2], the porting effort wouldn't be much painful, at least for the Plasma Components.<br>Please let me know what else we could make themable.<br>
It would require removing the interaction code from the Plasma Components and transforming it into a Style.<br>Obviously, this simplification of the Plasma Components would add these desktop components dependecy on Plasma.<br>
</div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
ignoring that for a moment, what i would like is:<br>
* still workspace look different at least potentially from the app look, even<br>
if just a different default theme<br>
* themes completely pixmap/svg//graphics based, no code involved, not even qml<br></blockquote><div> </div><div>This would be perfectly covered. We are also carrying on with the project what we call CustomStyles.<br>This styles set is a helper for creating styles using pixmap/svg/graphics.<br>
<br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
* for sure nothing based on qstyle ;) </blockquote><div><br>Surely not. :-)<br> <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
as capabilities, overall i like framesvg (way, way more powerful than<br>
BorderImage that i quite dislike), speaking of not retrocompatible changes..<br>
there are things that revealed to be pretty painful, like having to have the<br>
borders actually splitted in different elements rather than split the rendered<br>
pixmap afterwards, having to design the thing from scratch i would make it<br>
behave in a radically different way.<br>
<br>
main concern is mostly performance on scene-graph since it would have to be a<br>
QQuickPaintedItem, meaning resize the svg, paint it in software on a texture,<br>
and upload the new texture every time, but there could be no way around it,<br>
any way is chosen in the end. </blockquote><div><br>That's true.<br>But enabling themes/styles in QML can makes them free from QQPI for<br>new styles that can be written.<br> <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Cheers,<br>
Marco Martin<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br>
</div></div></blockquote></div><br>[2] <a href="http://codecereal.blogspot.com.br/2012/04/qml-themingstyling.html">http://codecereal.blogspot.com.br/2012/04/qml-themingstyling.html</a><br><br>Br,<br><br clear="all">Daker Fernandes Pinheiro<br>
<a href="http://codecereal.blogspot.com">http://codecereal.blogspot.com</a><br>