It's been many years that I dream of a 3D interface to design, in a web browser, 3D objects with EMAO Workshop parameterized basic shapes.

I was looking for a simple way for users and based on available technology, without success, until now.

I recently discovered 3DVIA Dassault Systems technologies, that I started to handle. A simple plugin to install an application to develop 3D applications (experiences in the jargon of 3dvia) and a deposit on http://www.3dvia.com/ to make the experience accessible in a browser and voila... well ... almost, because you still have to master 3dviastudio, which requires a long learning time, which I prefer to devote to developing visualkit.com.

So I decided to organize a competition 3dviastudio and I came in touch with Dassault ...

By the time to obtain information on the feasibility of the project, two new browsers were released: Firefox 4 and IE9. In addition to natively SVG support, these browsers support a new standard: WebGL. I also found a javascript library on http://mrdoob.com/122/Threejs and a sample application that can serve as a starting point on http://mrdoob.com/projects/voxels/. It works with IE9 and FF4! Go to see it, it's a great job. There are also other libraries, but I have not tried with IE9. Beginners should go to http://learningwebgl.com, where they can find step-by-step lessons ...

Two interesting technologies with two opposing philosophies of development: the 3dviastudio that provides developers with an advanced user interface, with extensive use of the mouse and keyboard, and that of WebGL that can be developed only (for now) with an Text editor ...

So there! I thought it would be interesting to put these technologies to compete through a competition ... 3D developers, if you're interested, take your mouse or your keyboard!

If you wish to sponsor this competition, do your prize proposals! Developers need to be motivated to provide the consistent effort (but exciting!) necessary to achieve the requested objectives.

You have to build a web based 3d editor like software, and in a parallel way, create a documentation on how you design it and how you build it. It is the natural way you work (it should be) : you think about what you want to do, you write it (in case of something interrupts your work), and you implement it.

For the document explaining how to use the software, you have to put it in an on-line help.

I think all competitors have an equal chance to win. Be lazy, as a developer should be, do what is asked, no more, no less ...