QML Scene Graph has moved…

Published Friday January 28th, 2011 | by

The new repository for QML Scene Graph and the next generation of QML is located here:

http://qt.gitorious.org/+qt-developers/qt/staging/

The branch you want is “qml-team/qtquick2″

Happy hacking!

Did you like this? Share it:
Bookmark and Share

Posted in OpenGL, Painting, Performance, Qt Quick

12 comments to QML Scene Graph has moved…

Scorp1us says:

Any updates? What is the feature parity/status with the regular branch?

And let it be said that:
I for one welcome our velvety overlords to the staging area.

gunnar says:

The biggest change since switching from the previous repo, is the merge with mainline Qt/QML, which means a lot of bug fixes to the QML items and working input handling.

Tm says:

Will the Scene Graph be part of qt 4.8?

Scorp1us says:

Oh heck yes! I’m all over this then! I’ll try it t his weekend!

Everything is looking great. Thanks for the information!

TomCooksey says:

Is there still support for multiple renderer back-ends? I was hoping to find some time fairly soon to learn the code base by playing with this on some Mali HW. Wanted to see how hard it is to traverse the scene graph and render the opaque items front-to-back (which has performance benefits for Mali). Is this still possible?

PS: Hi guys!!! ;-)

gunnar says:

TomCooksey: There is support for multiple rendering backends. Right now the solution would be to install your own QSGContext in the QSGView before showing it and reimplement the virtual QSGContext::createRenderer() function. For just sorting front to back, you can simply modify the sort function in the qmlrenderer.cpp, though.

Scorp1us says:

Do I have to grab the whole branch, or can I just grab the declarative directory?
When I try to browse it (http), it errors out (This Git object is too large to be displayed in the browser)

I usually just have it tar everything up and get it that way.

michael says:

Any hints on what to do for better performance? With QML_SHOW_FRAMERATE=1 I can see that the paintEvent takes >60ms on average. With the raster graphicsengine its <20. And it's not a very complex scene.

gunnar says:

scorp1us: yeah, you need to pull the whole branch and check it out.
michael: I would be interested in what this scene contains and on which environment, because normally that is not what we see. We have only seen that on massive texture uploads, several mb”s pr frame, or when GL resorts to poor software rendering, but in general we see improvements in performance.

Scorp1us says:

C:Qt>git clone git://gitorious.org/+qt-developers/qt/staging.git
Initialized empty Git repository in C:/Qt/staging/.git/
remote: Counting objects: 531558, done.
fatal: The remote end hung up unexpectedly
fatal: early EOF

What am I doing wrong? It counts object at 50-25 per second.

Scorp1us says:

I am not having any luck with checking it out.
Be it git protocol (where it says server closed connection)
or via HTTP:
error: Unable to get pack file http://git.gitorious.org/+qt-developers/qt/stagin
g.git/objects/pack/pack-64bdc54b212977013b5bfa98511b8edf2c7eef4f.pack
transfer closed with 116502980 bytes remaining to read
error: Unable to find 8a441f3cf8a2cbc92861b7c55dd4664da4e8130b under http://git.
gitorious.org/+qt-developers/qt/staging.git
Cannot obtain needed object 8a441f3cf8a2cbc92861b7c55dd4664da4e8130b
while processing commit 8cb85d5cb47f06f01f70781e9762a716cabdc73a.
fatal: Fetch failed.

git is not winning me over. I’d also like to skip the whole repo and just pull the branch I need, which I can do in svn or perforce.

Commenting closed.