Fa3ien wrote:

> 
>> All basic flow-chart type stuff. Understood clearly by even 
>> non-programmers. Objects?
> 
> Would it be difficult to understand that a sphere is an object,
> with properties (position, size, texture...)  and methods (translate,
> rotate, copy,...) ?
> 
No, but it could be to a problem to understand that your internet socket 
isn't an object in the same sense. You can create a unifying mechanism, 
often known as OOP or similar, but you then have to code the sphere 
something like

new Sphere s;
s.Position=[1,1,10];
s.Radius=.7;
s.Texture.Pigment=[0,1,0];
s.Scale(1,2,1);
s.Rotate(30,0,0);

That is all very clear coding, but *not* what most of the group here 
wants. POV4 should be easy to understand in it's most basic declarative 
form. Which in my opinion means that objects as virtual representations 
of things visible in your scene will have a different status and 
different syntax than all other 'objects'. Borrowing standard OOP 
language may be rather confusing in that respect.

Post a reply to this message