[Qt-interest] Clarification on "out of scope" closed bug

[Allen Bierbaum]

On Tue, Jan 18, 2011 at 10:45 PM, Thiago Macieira <thiago at kde.org> wrote:
> On Tuesday, 18 de January de 2011 23:29:40 Thiago Macieira wrote:
>> On Tuesday, 18 de January de 2011 16:54:19 Allen Bierbaum wrote:
>> > Our entire application is based upon using QGraphicsProxyWidgets.  We
>> > use them to place widget panels (floating windows, etc)  in a scene
>> > overlaid on  an OpenGL canvas.  This lets us do compositing and many
>> > other advanced visual effects and back when we created it, the
>> > recommended way to do this was QGraphicsProxyWidgets.  If this isn't
>> > recommended/supported any more, I hope there is a relatively easy
>> > migration path so we don't end up down a dead end.
>>
>> The migration path is to redo your widgets entirely in Graphics View.
>
> Or, better yet, in QML.

I agree with the other comments in this thread.  I *love* Qt and have
never regretted using it as a base.  It is stable, well documented,
elegant in design, and just plain works.

The important question to me is what is the migration path away from
QGraphicsProxyWidgets.  As another poster pointed out, we find the
power of using all of the suite of QWidget's to be a huge win.  I
remember the first time I heard that you were making it possible to
render these in OpenGL on top of a canvas.  I was blown away by the
possibilities that opened up and we have made heavy use of them to
create some pretty kick but interfaces.  In our usage we haven't seem
performance problems (last I checked the UI is rendering at > 100 fps
when we aren't doing heavy 3D rendering in the underlayed OpenGL
widget)

I am fine with moving away from QGraphicsProxyWidgets, but I can't
redesign our entire codebase to use QML or rewrite the entire QWidget
hierarchy in Graphics View items.

Is there any other way to bring the power and native feel of the
QWidget Hierarchy into a canvas view?  Are there any plans for Nokia
to provide (re)-implementations of all the QWidgets as something that
would work along with designer support for creating complex layouts?

I am not trying to complain, I understand the "we make mistakes"
comment.  I just want to know if there is a path forward I should be
trying to get onto without rewriting the entire codebase.

-Allen

>
> --
> Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
>  Senior Product Manager - Nokia, Qt Development Frameworks
>      PGP/GPG: 0x6EF45358; fingerprint:
>      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
>
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at qt.nokia.com
> http://lists.qt.nokia.com/mailman/listinfo/qt-interest
>
>