Feature #2305



Added by Anonymous over 10 years ago. Updated over 9 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:



Is there any planned development for something similar to Qt3D that would work with the WGLWidget ?

Some sort of scene node based graph.

Actions #1

Updated by Wim Dumon over 10 years ago

No. I admit I haven't looked at supporing a scene graph, but my first idea would be to see if it's possible to support an exising scene graph library in Wt rahter than to construct a new one. Ideas welcomed.

A 3D charting library is however in the pipeline.



Actions #2

Updated by Alan Jesser over 10 years ago

You might be able to borrow ideas from which tries to follow the STL format. There is also a JS library that someone created based on it.

Both have more than just scene graph features but looking at it might prove useful.

Actions #3

Updated by Mathieu Vadnais over 10 years ago

Funny you mentioned OSG. I just found this... ->

Actions #4

Updated by Wim Dumon over 10 years ago

Nice, I didn't know about that!


Actions #5

Updated by Koen Deforche over 10 years ago

  • Assignee changed from Koen Deforche to Wim Dumon
Actions #6

Updated by Koen Deforche about 10 years ago

  • Target version deleted (3.3.2)
Actions #7

Updated by Mathieu Vadnais over 9 years ago

Would it be possible to merge the ReWeb3D fork back into the master branch of Wt ? If it is, I would submit a pull request (as I have done some work on that).


Actions #8

Updated by Prasad Dixit over 9 years ago

ReWeb3D's wt wrapper exists because OpenGLES2 applications are not easily portable to Wt because of the way WGLWidget's 'gl' interface is designed. Although technically it seems very possible. (See:

I found myself writing a wrapper for WGLWidget because I also have code base for a 3D application written using OpenGL ES. I am trying to port it to Wt but WGLWidget's functions don't have 1-1 mapping with OpenGL ES ('gl' prefix for enums and functions is dropped. Functions parameters are different in some cases). As we are developing Desktop/mobile and Web app simultaneously, it is not a one time port. It will be a continuous work and not having 1-1 mapping with OpenGL ES is a going to be a inefficient and will result in unnecessary waste of time and maintenance overhead.

Wt is a C toolkit for Web closely emulating Qt. That being said, I should be able to port code written in C, OpenGL ES, and Qt with as minimal modification as possible. That is what make Wt attractive to me. Current interface of WGLWidget breaks that 'promise'.

As Wt becomes more popular (which I hope it will), there will be many developers who will find themselves in a similar situation as me. I hope Wt team takes notice of my concern. I think Qt's QGLWidget has done its OpenGL ES interface smart and right. I hope Wt's WGLWidget offers similar interface and developers don't need to develop there own wrappers.

Actions #9

Updated by Alan Jesser over 9 years ago

Someone correct me if I'm wrong but I don't believe the WGLWidget was designed to emulate OpenGL ES it was designed as a wrapper for WebGL. The server side rendering was added later, IIRC.


Also available in: Atom PDF