Thanks. I never thought of using Google ;-)

Sadly Google shows me what *they* want me to see, not necessarily what I am 
actually looking for.

Hence asking the question here: amongst a group of Qt experts who are not 
controlled by revenue-generating curating algorithms and who could point me to 
the most appropriate articles for my questions.

Thanks for the links. I will check them out and hopefully they will give me the 
info I seek.

-jct

> On 12 Jul 2016, at 16:38, Mitch Curtis <mitch.cur...@qt.io> wrote:
> 
> Have you tried Google? :D These two links probably cover your first two 
> questions:
> 
> http://doc.qt.io/qt-5/qtquick-visualcanvas-scenegraph.html
> http://doc.qt.io/qt-5/qtquick-visualcanvas-scenegraph-renderer.html
> 
> 
>> -----Original Message-----
>> From: Interest [mailto:interest-bounces+mitch.curtis=qt...@qt-project.org]
>> On Behalf Of John C. Turnbull
>> Sent: Tuesday, 12 July 2016 4:06 AM
>> To: Uwe Rathmann <uwe.rathm...@tigertal.de>
>> Cc: interest@qt-project.org
>> Subject: Re: [Interest] Utilizing the GPU, how to start?
>> 
>> Anyone?
>> 
>>>> On 10 Jul 2016, at 23:23, John C. Turnbull <ozem...@ozemail.com.au>
>>> wrote:
>>> 
>>> I am still new to Qt but am very interested in the technology and the
>> deep innards of how it functions. I have worked in a 3D animation studio
>> and learned a lot while I was there.
>>> 
>>> Is there documentation or articles that:
>>> 
>>> 1) Describe in detail how the Qt Quick rendering pipeline is designed
>> and how it operates.
>>> 
>>> 2) Describe the structure and overall architecture of the Qt Quick
>> Scenegraph and how it is rendered?
>>> 
>>> 3) Describe the steps that have been taken so far and any further steps
>> planned to optimise both (1) and (2)?
>>> 
>>> I really want to know how all this hangs together as I may be able to
>> further optimise and improve aspects of them.
>>> 
>>> -jct

_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Reply via email to