May be I wrongly expressed: imagine a 3D game whose model world is in
Pharo then rendered in Blender (I guess model data need to be share
between Pahro and Blender, but graphic only reside on Blender). Now you
could use the Pharo dev tools like inspector & al. to play with your games.
With DrGeo analogy: it will be more like a shared 3D model between Pharo
and Blender, and controlled from Pharo.
Le 15/09/2014 11:02, kilon alios a écrit :
It depends what you mean by control blender. Blender is 2 things a)
C/C++ source code that implements all features that users use b) the
Python API that allows to use all features that a user can use. Ephestos
already allows full access to (b) . So for example if you wanted Dr Geo
to export its data to blender so Dr Geo can convert its geometry to 3D
and use all the nice features of blender you can do that already with
ephestos. But for modifying existing functionality you need to get your
hands dirty with the source. Implementing new fuctionality like
importers / exporters etc is also doable via API so its doable via
Ephestos. But cpu intense new fuctionality is done by modifying the source.
--
Dr. Geo - http://drgeo.eu
iStoa - http://istao.drgeo.eu
