On Thu, Sep 22, 2011 at 10:29 AM, <[email protected]> wrote: > - Add Support for Tree Views (Hard to do without hacks or extending Qt Quick)
I agree. I think TreeView and TableView components need to be implemented in C++ as a plugin extension or as new components in QtQuick2. The problem of the first approach is that we would end up duplicating code to avoid some QML private header dependencies, like the Flickable API. Currently, I'm mimicking TableView elements using ListView with special delegates, like qt-components, but that seems unnatural and it also generates a great overhead due the delegates' bindings. > - Write more examples and applications to verify and test the API More examples would be nice. I think as soon as all the missing features are solved more applications will come. > - Research Layouts. (I am still not sure if creating new QML Layouts are > really required, but I would love to see some research on this. Dynamic > spacing between different controls is one issue that we do not have a > solution for.) A proof-of-concept would be great on this area. Currently, I'm stuck with some project deadlines, but I think I can look on this in my spare time. > - Refactor QStyle for Qt5 to remove the QWidget dependency It would be really nice if this dependency could be removed. Probably a new style API that renders in a QImage would suffice; using that image to generate a GL texture in the end. Do you have any thoughts on this? Br, Adriano _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
