On Wed, 28 Sep 2011 05:28:53 +0000, gunnar.sletta wrote: > We have talked about two classes to support mixing and neither of them > are started. > > Embedding QML 2 into Widgets: Used to put QSGView classes into existing > QWidget/QGraphicsView apps. The primary usecase is when doing a bit of > QML inside a complete QWidgets based app like your usecase, typically > when gradually porting your app from a QWidget based stack to QML 2. > > Embedding of QWidgets into QML 2. Similar to the QGraphicsProxyWidgets > class. The primary usecase being when an application is written in QML > wants to make use of an existing QWidget based component, like a text > editor.
As author/maintainer of a 3rd party widget library ( Qwt ) I'm wondering how my project can survive in the situation of having 2 different worlds. For technical plot types like spectrograms, scatter plots etc I can't imagine that something like QML could be the weapon of choice ( maybe I'm wrong ). But for configuring attributes like scales, fonts, palettes or less data intensive business charts ( bar plots, financial charts ) QML should be a an option. Hope it's obvious why I'm not excited about the idea of implementing the same library twice - but what could be the concept for supporting both worlds ? I can imagine to introduce a layer where I can hide if my rendering code ( = translating plot items into graphic primitives ) is supposed to run with QPainter or any other API - as long as it is available from C++ - and I could try to write some code on top of the plot classes that does what needs to be done to make it available for QWidget/C++ or QML. Did you ever discuss the situation of 3rd party widgets and do you have an advice ? Uwe _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
