<div class="gmail_quote">2011/3/4 Marco Martin <span dir="ltr"><<a href="mailto:notmart@gmail.com">notmart@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi all,<br>
since months we are repeating how beautiful plasma2 will be with scene graph<br>
and how it will save the world ;)<br>
for an overview of the planned changes at the moment, here it is:<br>
<a href="http://community.kde.org/Plasma/libplasma2" target="_blank">http://community.kde.org/Plasma/libplasma2</a><br>
<br>
abstract talk is nice, but to have a more clear idea<br>
today i've been hacking on a little on a simple mock prototype to just check<br>
if some needed things are possible, and if the api i'm thinking about makes<br>
sense:<br>
<br>
<a href="http://quickgit.kde.org/?p=scratch%2Fmart%2Fplasma2-proto.git&a=summary" target="_blank">http://quickgit.kde.org/?p=scratch%2Fmart%2Fplasma2-proto.git&a=summary</a><br>
<br>
to try it it's needed to build Qt from gitoious, staging clone, qml-<br>
team/qtquick2 branch.<br>
<br></blockquote><div><br>Cool!<br><br>So now that we're thinking of an api i have a question: about applets grouping. Do we want it still outside of libplasma? If yes i'm ok with it, but i'd really need some things in the api, the most important a PlasmaItem or whatever, parent of Applet in the class hierarchy, with some common things like config() and containment(). I would then make my AbstractGroup subclass from that and it would avoid me a lot of duplicates function with Applet* and AbsractGroup*.<br>
<br><br>Giulio.</div></div><br>