Anestis Koutsoudis from the Cultural and Educational Technology Institute has just sent us a link to another show-case using digitized 3D content. This is now the third x3dom project from the cultural heritage field.
These models have even more polygons and better textures and look impressively good for web content.
We already have a quite active forum, but some users (and developers) really prefer email-lists and there it is:
Feel free to post any question, comment or links to your own cool x3dom-application on the list.
(Side node: This is still hosted on sourceforge even so we will move the code repository to github soon, but github does not provide email-lists.)
The X3D spec includes the SAI (Scene access interface ) API to manipulate the scene during runtime. X3DOM uses the DOM for this purpose. However, we need a small API to access runtime properties which are not reflected through the DOM-structure. Therefore we have started to create an runtime API for X3DOM. Such an API would allow the developer to access and modify various runtime dependent parameters of the 3D scene and the renderer. For example: resetting views, cycling cameras or changing navigation modes. We are pleased to annouce that a first revision of this API is now available in the latest development version of X3DOM.
You will find examples of API functionality in action here: http://x3dom.org/x3dom/example/x3dom_runtime.html
Developer API documentation can be found at: http://x3dom.org/x3dom/doc/api/ (we are still improving this, so give us some slack on that front).
Be aware that this API might change until the next stable release of X3DOM. If you are hotlinking the development version from this sever, please track the commit logs of the source repository for changes that might break your code.
In the meantime, we hope you enjoy experimenting with the new API functionality and we are very appreciative of any feedback you might have.