POV-Ray : Newsgroups : povray.general : dreams of POV 3.5 and 4.0 : Re: dreams of POV 3.5 and 4.0 Server Time
12 Aug 2024 01:29:53 EDT (-0400)
  Re: dreams of POV 3.5 and 4.0  
From: Margus Ramst
Date: 13 Apr 1999 19:19:26
Message: <3713c2ee.0@news.povray.org>
Anthony Bennett wrote in message <3713539C.F22AAB8E@panama.phoenix.net>...
>
>This, too, is my dream. I can't wait to see the day when I can throw my
>Superpatch away, and free up a few megs. =) (God bless Ron Parker!)
>

I hope and pray this day will not come, and that Ron (or somebody) will
continue the effort of combining all the unofficial patches into one
"superpatch". This will be no less useful after 3.5

>
>FK and IK and an addition of most of the things we don't have when compared
>to the $$$ packages would be nice. Of course, if they can toss in a little
>speed increase that would be cool too. I just don't think that OO is the
way
>to go. Things are fine as they are. I imagine 4.0 as a new interface, more
>speed, and more stuff available kinda thing. I dream of it including the
>things we would like to have, like FK and IK, and collision detection and
>whatnot, but not as a change in the language, which I find quite good. I

IK is already available in Moray (which is hardly a $$$ package); I suppose
it could also be done with the current #macros, given time and expertise.
Not that I'm opposed to the idea, of course. But there are other things that
should have a higher priority.

I have nothing against OO as such, _provided_ that the language maintains
backward-compatibility. Not because I wouldn't be willing to learn the new
language. But too much previous work would go to waste.

Your mini-studios concept is certainly interesting and novel. But it would
pretty much be a duplicated effort. There are several free/cheap modellers
for POV, which can do this and much more. If only any of them could read POV
files, I'd be a happy puppy.

Something I would really like is the ability to access POV's internal
functions. Like trace, min_extent and max_extent in the Superpatch
(incredibly useful functions, IMO), but also reflection, refraction, pigment
or any other texture property at an intersection point, light intensity at a
given point in space, etc. etc. These are, of course, just of-the-wall
examples, but you can see what I'm referring to.
I would, of course, also applaude the addition of collision detection.

Margus


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.