>par### [at] my-dejanewscom (Ron Parker) writes:
>
>> If you make a Tk interface, please keep in mind that some of us might
>> want to use it with Perl/Tk.  
>
>  Sorry guy, I think I'll do it in Python. Not because I think it's
>better than Perl (I have _never_ written any Python yet, don't charge
>me for religion wars), but because I want to try it.
>
>> Also, keep in mind that the new POVLEGAL
>> specifically forbids making new interfaces, so you won't be able to
>> distribute your changes without the blessing of the POV-Team.

He is refering to the last paragraph:

=>To allow POV-Ray to interface with outside programs, the official
=>versions of POV-Ray include several "hooks" for it to call other
=>tasks.  For example: the generic part of POV-Ray provides
=>operating system shell-out commands. The Windows version has GUI-
=>extension hooks and the ability to replace the text editor.
=>Modification to these hooks or other officially supported
=>interface mechanisms to increase functionality beyond that of the
=>official version IS EXPRESSLY PROHIBITED.

How do you read it?

>  Er... <URL:http://www.povray.org/docs/pov3002f.htm#ref 40 pri 0>
>does not say a word about making interfaces. And my
>/usr/local/lib/povray3/povlegal.doc does not either. So for now I
>haven't heard of such limitations. Maybe both of these are out of date
>(you seem to refer to a new one), but even in this case, there's no
>way I'll download a Windows version just for this file. So, could you
>please send (or post) the part of this file you're referring to?

I posted it in povray.binaries.programming as "POVLEGAL.DOC for POV-Ray 3.1"


Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany

Post a reply to this message