"Samuel Benge" <stb### [at] hotmailcom> wrote:
> It's one rlp object copied, translated and rotated.

Oops, it was *not* rotated. I shouldn't type on autopilot :)

Post a reply to this message

>
> Attached is a demo image I never posted (I think).

This looks fabulous. Thanks for posting the code again (and the link to your
earlier demo image.)

Post a reply to this message

Thanks Sam! Excellent stuff.

Note:
In rlp_Shapes.pov, the object square is not allowed. It should be 
Square, as it otherwise refers to the square pattern.

Always better to use upper case letters to start ;-)

Thomas

Post a reply to this message

Thanks guys!

Thomas de Groot <tho### [at] degrootorg> wrote:
> Note:
> In rlp_Shapes.pov, the object square is not allowed. It should be
> Square, as it otherwise refers to the square pattern.
>
> Always better to use upper case letters to start ;-)

Version 0.2 was released before I started using uppercase letters for
everything. Somebody once mentioned how even seasoned povvers sometimes use
lowercase letters for their variables, and how said case might eventually
interfere with POV's reserved keywords, so I've tried to use uppercase ones ever
since. I might have to release another version simply for that :)

Post a reply to this message

"Samuel Benge" <stb### [at] hotmailcom> wrote:

>
> Version 0.2 was released before I started using uppercase letters for
> everything. Somebody once mentioned how even seasoned povvers sometimes use
> lowercase letters for their variables, and how said case might eventually
> interfere with POV's reserved keywords, so I've tried to use uppercase ones ever
> since. I might have to release another version simply for that :)

OMG, I almost never use capital letters for variables :-O

But then again, my variable names are almost never as simple as
#declare aaa = 45;
They're partial sentences(!)--like...
#declare rotation_for_my_cylinder_object_around_ground_heightfield = 45;

Lots of typing of course--thank God for cut-and-paste! ;-)

But for me, this removes a 'level of abstraction' in my scene code, so I easily
know where to go when there's a problem, or I want to change something without
having to think too hard about it.

The trouble comes if I want to post my code--then I have to go back and
*simplify* the names. Using capital letters for that is probably a very good
idea!

Post a reply to this message

On 7-3-2013 8:29, Kenneth wrote:
> "Samuel Benge" <stb### [at] hotmailcom> wrote:
>
>>
>> Version 0.2 was released before I started using uppercase letters for
>> everything. Somebody once mentioned how even seasoned povvers sometimes use
>> lowercase letters for their variables, and how said case might eventually
>> interfere with POV's reserved keywords, so I've tried to use uppercase ones ever
>> since. I might have to release another version simply for that :)

I regularly have to remind myself too...

>
> OMG, I almost never use capital letters for variables :-O

You have sinned against the First Rule of POV-Ray  ;-)

>
> But then again, my variable names are almost never as simple as
> #declare aaa = 45;
> They're partial sentences(!)--like...
> #declare rotation_for_my_cylinder_object_around_ground_heightfield = 45;
>
> Lots of typing of course--thank God for cut-and-paste! ;-)
>
> But for me, this removes a 'level of abstraction' in my scene code, so I easily
> know where to go when there's a problem, or I want to change something without
> having to think too hard about it.

I know what you mean. While not as extreme as your example, I often use 
long words too.

>
> The trouble comes if I want to post my code--then I have to go back and
> *simplify* the names. Using capital letters for that is probably a very good
> idea!

Absolutely.

Thomas

Post a reply to this message

"Kenneth" <kdw### [at] gmailcom> wrote:
> But then again, my variable names are almost never as simple as
> #declare aaa = 45;
> They're partial sentences(!)--like...
> #declare rotation_for_my_cylinder_object_around_ground_heightfield = 45;
>
> [snip]
>
> The trouble comes if I want to post my code--then I have to go back and
> *simplify* the names. Using capital letters for that is probably a very good
> idea!

Nothing wrong with long variable names.  It's not like we're using FORTRAN IV
with 4096 bytes of RAM.  I think it will matter only if you're posting a
library, where the users will be frequently typing your variable names into
their scene files.

Post a reply to this message

Thanks, Sam!

Note to Linux and Unix users: the file rlp_Bevels&Types.pov has to be quoted in
order to render.  E.g.:

   povray 'rlp_Bevels&Types.pov' +a

Post a reply to this message

"Cousin Ricky" <rickysttATyahooDOTcom> wrote:
> Note to Linux and Unix users: the file rlp_Bevels&Types.pov has to be quoted in
> order to render.  E.g.:
>
>    povray 'rlp_Bevels&Types.pov' +a

It just occurred to me: could Sam's upload have failed because the Object
Collection server software choked on the ampersand?

Post a reply to this message

> Nothing wrong with long variable names.  It's not like we're using FORTRAN IV
> with 4096 bytes of RAM.

No but we're still using an editor without auto-complete capability.

Post a reply to this message