On Tuesday 23 March 2010, Alexis Ménard wrote:
> On Wed, Mar 24, 2010 at 4:15 AM, Marco Martin <notmart@gmail.com> wrote:
> > On Tuesday 23 March 2010, Aaron J. Seigo wrote:
> >> On March 22, 2010, Alexis Ménard wrote:
> >> > Hello,
> >> > 
> >> > I just wonder which part of the Plasma bindings we want to put into
> >> > QML :
> >> > 
> >> > http://techbase.kde.org/Development/Tutorials/Plasma/JavaScript/API
> >> > 
> >> > All the UI related stuff is pretty much useless because QML provides
> >> > those facilities. It would be nice to have a list so we can think
> >> > about what we can do for it.
> >> 
> >> the UI related API can be divided (roughly) into three bits:
> >> 
> >> * the classes in kdelibs/plasma/widgets/ being loaded via the QObject
> >> bridging provided by QtScript. we should have those widgets available
> >> from QML.
> > 
> > as far i seen it's pretty easy to bind any qgraphicswidget into qml..
> > the bad news is that it will behave as a second class citizen not being a
> > QDeclarativeItem, so can't be in a qanchorlayout ar directly be a
> > listview delegate for instance, everything will have to go for a proxy
> > object called GraphicsObjectContainer, i'm still a bit uneasy with this
> > one.
> 
> This is about to change. QGraphicsObjectContainer will disappear.

kisses :D


-- 
Marco Martin
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel