I admire your attempt to motivate change. It seems like you invested a
lot of time writing this. POV-Ray is indeed in need of a facelift, but now
is not the time, and words alone do not make POV better. As I have learned,
personal action is of the escence to improve POV-Ray.

   If you want things to be more like you plan them, then get your hands
dirty and code till you wear your fingers down to a nub - prove that it can
be done. I, luckily, am still in the nose-in-the-books phase. I have much to
study - and practice, before I open my mouth again on any feature-requests
and the like (some of which I will hopefully back up with at least
pseudo-code).

   If you are unable to code, then at least do what I did to get Blinn
shading into MegaPOV: help the coders by doing some research for them. They
have a limited amount of time - this being their 'hobby' - and they spend
most of it coding, not researching. Also, a wish-list such as yours sounds
much sweeter to the ears with some papers/pseudo-code/code to back it up.

   As for your suggestions, yes, some of them sound valid, but others do
not. First of all, you should have known - if indeed you are so interested
in POV as to write this big long manifesto/proposal/whatever - that POV-Ray
3.5 is close to being completed, and indeed has many of the features you say
you would like POV to have. So be glad at least that some of your wishes
magically came true. Mine took much longer to reach fruition.

   Second, it would have also been wise on your part to read previous
discussions on the matter of OO'ing the POV SDL, to find out why the Team is
not persuing implementing it yet. That way you wouldn't have simply repeated
things we've read before, and might have found out that such a thing is in
the pipeline for indefinite future versions.

   Third, this suggestion of using C++ is also redundant, as you should have
noticed that the Team announced long ago that 4.0 would be done with it.

   To make a long story short: read before you write, study before you code
(so the Team doesn't spend months fixing it), code before you demand,
research and contribute thusly if you cannot code, and try not to rock the
boat.

   I could say a whole lot more to you, but my fellow POVers have said it
for me, so no need to repeat. Good day to you. Do not feel that we are
shunning you. Just pay more attention from now on, OK? :)

--
Anthony Bennett

Post a reply to this message

On Thu, 10 Jan 2002 15:09:43 +0200, Eugene Arenhaus
<eug### [at] avalon-netcoil> wrote:

>Example 1. 

portal pigment, MegaPOV

>Example 2.

object pattern, POV 3.5

>Example 3.

isosurfaces, parse-time hf generation, POV 3.5

>All properties of objects in the scene should be accessible from the
>scene description language, both for reference and assignment.

min_extent, max_extent, #declare, transform, vtransform, vector/float
functions, POV 3.5

>It should be possible to use references to objects instead of object
>copies.

mesh2, POV 3.5

...

sorry, need sleep. This should be enough for now :)


Peter Popov ICQ : 15002700
Personal e-mail : pet### [at] vipbg
TAG      e-mail : pet### [at] tagpovrayorg

Post a reply to this message

In article <nmpu3uc9ks523edtc1li7uv3c4sfbv902m@4ax.com>,
 Peter Popov <pet### [at] vipbg> wrote:

> >Example 1. 
> 
> portal pigment, MegaPOV

MegaPOVPlus, and an unreleased version...
I really should update my website...I don't plan to release a new MP+, 
at least until a MegaPOV based on 3.5 is released, but maybe I'll 
release the particle system and portal pigment patches individually.


> >Example 2.
> 
> object pattern, POV 3.5

Or just a combination of patterns and maps, POV 3.1....probably earlier 
versions. More difficult though.

-- 
 -- 
Christopher James Huff <chr### [at] maccom>

Post a reply to this message

In article <3c3f7645$1@news.povray.org> , "Rick [Kitty5]" <ric### [at] kitty5com>
wrote:

> wrote:
>> > my point being you cannot take a pov 2.2 file and expect pov 3.5 to
> render
>> > it without some tweaks
>>
>> have you checked this?
>
> I have spent hours doing conversions

Did you ever try "#version 2.2" in those scenes?

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

> Did you ever try "#version 2.2" in those scenes?

no, as I wanted to use objects from an older pov file in a new scene


--

Rick

Kitty5 WebDesign - http://Kitty5.com
POV-Ray News & Resources - http://Povray.co.uk
TEL : +44 (01270) 501101 - FAX : +44 (01270) 251105 - ICQ : 15776037

PGP Public Key
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x231E1CEA

Post a reply to this message

"Rick [Kitty5]" wrote:
> 
> > Did you ever try "#version 2.2" in those scenes?
> 
> no, as I wanted to use objects from an older pov file in a new scene

Hint: You can use the version directive more than once in the same
scene file.

-- 
Ken Tyler

Post a reply to this message

In article <3c40aecd$1@news.povray.org> , "Rick [Kitty5]" <ric### [at] kitty5com>
wrote:

>> Did you ever try "#version 2.2" in those scenes?
>
> no, as I wanted to use objects from an older pov file in a new scene

???  You are aware that you can use #version 2.2 when the old part starts
and then switch back to #version 3.x after the objects have been parsed.  It
is in the documentation...

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Rick [Kitty5] <ric### [at] kitty5com> wrote:
: a little pointless as pov 4 will (hopefully) be C++ instead of C?

  3.5 is already C++ (although mostly in the sense that it requires a C++
compiler, not in the sense that it has been designed as OO C++ from the
beginning).

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

Peter Popov <pet### [at] vipbg> wrote:
:>It should be possible to use references to objects instead of object
:>copies.

: mesh2, POV 3.5

  Also mesh, POV ?.?

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

> a little pointless as pov 4 will (hopefully) be C++ instead of C?

Whatever.

Tony[B] has stated much more eloquently what I intended to convey. :)

^"^

Post a reply to this message