In data lunedì 14 gennaio 2013 16:30:15, Aaron J. Seigo ha scritto: > the real fix, however, is not to do the UI in python. use QML.
Speaking of that, how does Plasma (or the workspace in general) fit when using QML, according to these 3 definitions (taken from the PyQt docs): 1. Pure applications that are written entirely in QML and can be run using the qmlviewer tool provided with Qt. PyQt4 fully supports this type of application. 2. QML allows QObject instances to be used in QML applications. QML code is able to call an object’s slots and has read and write access to the object’s properties. QML code can also respond to changes to the value of a property. PyQt4 fully supports the use objects created in Python in this way. T 3. QML also allows QObject sub-classes to be used in QML applications so that new instances are created from QML. PyQt4 does not support this. The reason is that QML uses information generated at compile time (specifically it uses QObject::staticMetaObject) rather than information created dynamically at run time (i.e. QObject::metaObject()). This approach is fine for a static language like C++ but causes problems for languages such as Python that allow types to created dynamically. This may be important for users of bindings. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
