[Kde-games-devel] Re: Qt5 outlook
Parker Coates
parker.coates at kdemail.net
Fri May 13 17:29:04 CEST 2011
On Fri, May 13, 2011 at 04:46, Stefan Majewsky wrote:
> Hey everyone,
>
> I've been following the qt5-feedback list since it was announced, in
> order to ensure that our requirements are well represented. The most
> impacting topic for us is probably Qt Quick 2. Here is the executive
> summary:
> 1. Starting with Qt 5, Qt Quick 2 (i.e. QML objects on an OpenGL
> canvas) will be the recommended way to create user interfaces, with
> QWidgets being available as a compatibility layer.
> 2. QGraphicsView and friends is considered stable, and still
> recommended for rendering big numbers of items, since QGraphicsItems
> have less overhead than QML's QObject-derived elements.
> 3. Qt3Support is obviously going away.
>
> What does this mean?
> 1. For any new code, the single best choice for a canvas currently is
> QGraphicsView, supported by KGameRenderer as necessary. In the long
> term, we can look at migrating game canvases to Qt Quick 2, too, in
> order to take advantage of the capabilities of OpenGL (i.e.
> bling-bling) and to simplify the codebase.
More information about the kde-games-devel
mailing list