Patrick Elliott wrote:
> 
> Would this imply that it may then become possible to use a more simple 
> front end or even create one as a module that could one Windows be an 
> ActiveX control or a Python app on Linux, etc? In other words, strip off 
> the existing front end and make one that can be tied into another 
> application, as long as appropriate information is provided to state that 
> the backend is in fact POVRay when its first loaded? I mean the plugin 
> system that is available and programs like Moray use is nice, but I felt 
> it always did leave a bit to be desired in some cases.

First of all a dynamically linked frontend and a stripped-down backend 
would violate the spirit and the letter of the current license - this 
has been explaind in depth in the past including the lack of possibility 
to simply change the license.

Apart from that what you wrote does not mention what you think would be 
possible by dynamically linking the POV-Ray backend with a different app 
that is not possible to do via stdin and stdout of the official version. 
  Note i am not saying such things don't exist but you have not 
mentioned any.  One thing i could think of is the possibility to pause 
and resume a render (without stopping it) but this would be quite simple 
to add by having POV-Ray interpret pause and resume commands from stdin.

BTW i just announced a program in tools.general that demonstrates how 
you can integrate POV-Ray into another program using these means.

Christoph

-- 
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 03 May. 2005 _____./\/^>_*_<^\/\.______

Post a reply to this message