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. * bindings for the QGraphicsLayout classes. those are unneeded in QML. * QPainter and related; we don't need any of that since there is no direct painting in QML. the bindings for QRectF, QPoint, QColor, etc may or may not be of use, but are small and would be nice to have if QML doesn't already provide for nice programmatic access to things like colors. all the rest of the JS bindings, which are mostly about things other than GUI, ought to be in there. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
