Am Do., 10. Jan. 2019 um 18:07 Uhr schrieb Uwe Rathmann <uwe.rathm...@tigertal.de>: > > On Thu, 10 Jan 2019 14:21:59 +0000, Kari Oikarinen wrote: > > >> True, but Qt/Charts is also QWidgets only. > >> > > Not quite: https://doc.qt.io/qt-5/qtcharts-qmlchart-example.html > > It's the first time I checked this code, but if I'm right I would say, > that with Qt/Chart over QML the plot scene is never rendered hardware > accelerated ! > > This is actually worse than any other pure widget based solution - > including Qt/Chart widgets - that could at least take advantage of using > hardware acceleration over X11 or OpenGL.
There is a property that enables OpenGL rendering for _some_ plots and it has some side effects: https://doc.qt.io/qt-5.11/qabstractseries.html#useOpenGL-prop > So what has to be done for binding a plot widget to the scene graph and > for building a declarative API on top, that can be exposed to QML, is > more or less the same for any type of plot widget. It's a wrapper around > the plot classes and therefore no strong argument for not using an > existing solution. Basically yes, a Qwt QML wrapper is a solution that works with acceptable performance and it can be customized to blend in with the rest of the application (e.g. https://user-images.githubusercontent.com/2573046/40121913-ea4b6c34-5922-11e8-9f2e-a825fc1a2b1c.png ). However my guess is that most users expect something as simple as this: BarChart { model: myData } and they don't care about how it works as long as it works. But I don't see the Qt Company write wrappers for LGPL libraries when they OTOH try to convince their customers to not use LGPL and instead buy a commercial license. -- Regards Samuel _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
