At moment I’m again looking for a (small) scene-graph/3D-engine “thing” that works nicely with Qt.
I already got a lot of experience with some libraries that fit this category.
(I just did a update to the wiki, which more or less reflects my knowledge: http://qt-project.org/wiki/Using_3D_engines_with_Qt )
Some of them are giant utility pool, with so much stuff that I don’t need (and don’t want to understand).
Half of them are dead-project and most of the rest are worse documented.
So, about Qt3d … awhile ago I did a small hobby-project with v1.0 (qt4.*, pure C++) … beside the usual issues with jumping into a bigger/unfamiliar API, it worked nicely for me …
I only got one point where my needs fought against the API-Design:
I had the need to generate a geometry that has a fixed maximum number of vertices and indices … BUT dynamic and changing values and the number of “active indices” …
Figuring out how to change vertices-data is the first point, I think function naming is really worse at this point (setting value is possible by the non-”…At” getters, that’s by no way intuitive)
Figuring out how to do dynamic indices gets really trick ;) … if I remember correctly, I did it by subclassing the node-class and storing indices there (to hook into paint-virtual-function and do some magic) … oh, and I think I had to set dummy-indices in geometry to force uploading of vertices data …
So, back to the topic:
Is there anywhere a documentation what would be the next developments? (if Qt3D would be reactivated)
Is a refactoring of the C++ API possible/planned?
… if a refactoring would be OK (and I would find some time) … is the starting point a bug-entry? or a contribution? or something else?
↧