>Um, what's wrong with MegaPOV? I wouldn't call it "waiting in the dark" 
>with things like MegaPOV available...and perhaps you just haven't 
>noticed, but there has been a small explosion of new patches lately.

I love MegaPov, but we are being kept waiting in the dark as far as the 
actual development schedule is concerned.  If someone on this newsgroup 
asks when 3.5 will be released, they will get several "When it's ready" 
responses, which are pretty much useless.

>As for the license: modifying POV-Ray is allowed, it just has to remain 
>"POV-Ray"...you can't just strip out the renderer and use the parser, or 
>use code from it in your own projects, the modified version has to 
>retain the functionality of the official version. This seems to be quite 
>a reasonable requirement to me...or were you talking about the other 
>restrictions?

I, personally, have no desire to strip out the renderer and use the parser 
or anything of the sort, but I don't really see what harm there would be in 
doing so.  That's the whole idea behind OpenSource:  Sharing of source and 
ideas.  Peter Popov mentioned that some parts of PovRay were written by 
people who can no longer be contacted, and therefore using their code 
without restriction (and without their permission) could lead to trouble.  
Well, I don't think these people would've contributed their code with that 
sort of attitude; and, even if they had, are they really going to take the 
time/effort to cause trouble?

>And a much more "open" development model is planned for POV 4.0. For 
>more information, read the message "POV-Team Status Report - September 
>1, 2000" by Chris Cason in povray.announce.frequently-asked-questions.
>

This is a relief, but, at the current rate of PovRay development, I don't 
know if I'll live that long;-P

Post a reply to this message