Carsten Haitzler (The Rasterman) wrote:
>
>> Either way, this would allow for engine-specific extensions
>> for evas.. wrapping things adequately would allow for things like
>> say an "evas3D" lib if really desired.
>
> sure. 3d INSIDE a "3d object" i can deal with in evas :)
>
Exactly. Wrap things say a 3d-scene object and do your 3d stuff
'inside' such an object. One can do both immediate-mode and retained-
mode kinds of rendering to such a scene object. For the latter type,
one could have auxiliary 3d objects which must be 'bound' to such a
scene, with coordinates rel to the scene obj,... eg. a 3d-scene object
itself might be one such object that one could add to another, and
ideally all evas primitives would also be added to such a 3d-scene
object.
One can extend evas in various ways by suitably having such
objects which are like 'canvases' themselves that may support their
own kinds of rendering/object system... things like 3d, svg, html,
and many others are all possible in this way.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
