Cheap_Sweep.inc file should be posted to p.b.s-f by the time you read this.

Regarding this demo-pic. I have seen this type of knot before and was able
to figure out the function. I want to post this function for others to use
and would like to post it with the correct name. Does anyone know the name
of this function?

Feedback regarding the readability of my *.inc file would be *greatly*
appreciated. I spent literally 3x the amount of time commenting and cleaning
up this file as I did getting it to work. I have made the file very easy to
take a quick look at for any who would be willing to do so. There is a
sample file at the bottom, so there is no need to create macro input in
order to evaluate the macro.

It's should be worth downloading anyway, as it is a cool little macro.

Thank you,
 -Shay

Post a reply to this message

Attachments:
Download 'Cheap_DemoJPG.jpg' (27 KB)

Preview of image 'Cheap_DemoJPG.jpg'

I found a mistake.
line 92
#write (Sweep_Out, " cylinder {", Previous_Vx, ",", Next_Vx, ",", RADIUS,
"}\n")
should read:
<snip> Prev_Vx <snip>

If the macro seems to be posted twice in p.b.s-f, it is because I am
canceling my original post and replacing it with the corrected file.

 =Shay

Shay <sah### [at] simcopartscom> wrote in message news:3cac8a49@news.povray.org...

Post a reply to this message

This is an excellent macro, I'm really enjoying it.  Thanks!

"Shay" <sah### [at] simcopartscom> wrote in message
news:3cacbf11@news.povray.org...
> I found a mistake.
> line 92
> #write (Sweep_Out, " cylinder {", Previous_Vx, ",", Next_Vx, ",", RADIUS,
> "}\n")
> should read:
> <snip> Prev_Vx <snip>
>
> If the macro seems to be posted twice in p.b.s-f, it is because I am
> canceling my original post and replacing it with the corrected file.
>
>  =Shay
>
> Shay <sah### [at] simcopartscom> wrote in message
news:3cac8a49@news.povray.org...
>
>

Post a reply to this message

Spock <spo### [at] nospamcom> wrote in message news:3cacd07a$1@news.povray.org...
> This is an excellent macro, I'm really enjoying it.  Thanks!
>

I'm glad you are enjoying the macro. I am very interested in whether or not
you find the code to be clear and readable. I tried to make the algorithm as
clear as possible to any who read the macro so that they can optimise it for
their own applications.

 -Shay

Post a reply to this message

Well, to be annoyingly honest, I think I will leave macro writing and
maintenance to those of you who can understand it.  My brain barely
generates enough power to keep my mouth flapping, lord knows what would
happen if I had to think as well...

I'm just going to use it to make pretty pictures and let you know if
something doesn't seem right.  So far it seems wonderful :-)

"Shay" <sah### [at] simcopartscom> wrote in message
news:3cacd1de$1@news.povray.org...
>
> I'm glad you are enjoying the macro. I am very interested in whether or
not
> you find the code to be clear and readable. I tried to make the algorithm
as
> clear as possible to any who read the macro so that they can optimise it
for
> their own applications.
>

Post a reply to this message

Attachments:
Download 'Spline2.jpg' (48 KB)

Preview of image 'Spline2.jpg'

Shay wrote:

> Feedback regarding the readability of my *.inc file would be *greatly*
> appreciated. I spent literally 3x the amount of time commenting and cleaning
> up this file as I did getting it to work.

I haven't had the time to go through all of it, but the time you spent commenting
was appreciated by me. If I wasn't such a 'matrix idiot' then everything would be
clear :-)

> It's should be worth downloading anyway, as it is a cool little macro.

Indeed. Very fun to play with.

I did make a little modification of my own though, through personal taste. For
me, it's more intuitive to use object{} for something that sounds like an object,
so I made the macro spit out a union instead of a collection of torii.

MJL

Post a reply to this message

"Mark James Lewin" <m_j### [at] yahoocomau> wrote in message
news:3CACF5B5.A62D4BF9@yahoo.com.au...
> I haven't had the time to go through all of it, but the time you spent
commenting
> was appreciated by me.

I'm very glad to hear that


>If I wasn't such a 'matrix idiot' then everything would be
> clear :-)
>

The use of matrices should be very clear in the macro. If you have any
questions, feel free to ask me here or in Pov general. Once you have reached
a very basic understanding of matrices, a visit to
http://davidf.faricy.net/povre.html should clear up most remaining
questions. On thing missing from the site (to my recollection) is an
explanation of the combining of matrices. When you reach a point that this
knowledge is necessary, I or someone else will be happy to outline it for
you.

I was living under a bridge and digging ditches during the time in my life
when most here were in college. I did not know a thing about math until I
started seriously getting into Pov-Ray a few months ago. I am slowly
learning.

>
> I did make a little modification of my own though, through personal taste.
For
> me, it's more intuitive to use object{} for something that sounds like an
object,
> so I made the macro spit out a union instead of a collection of torii.
>


EXCELLENT. This is the reason for all of the comments!! I wanted the macro
to be clear enough that anyone would be able to easily modify it for their
own needs or wants.

 -Shay

Post a reply to this message

"Spock" <spo### [at] nospamcom> wrote in message
>
> and let you know if
> something doesn't seem right

Please do!

If the black banding in your spiral is not desired, using merge and placing
a sphere where each piece meets another will solve the problem.

I thought about adding a switch for this. I also thought about adding a
No_File and No_Image switch, but I decided against these things, as I would
only be obscuring the algorithm.

Instead, I chose to break the code into sections and leave lots of notes so
that others can quickly add these things if they so desire.

Thank you for your interest.
 -Shay

Post a reply to this message

> getting into Pov-Ray a few months ago.
> I am slowly learning.

Fast learning, in my honest opinion. You've got to have some programming
experience before POV-Ray, right?

Well, I started programming when I was 8 years old but it's not until today
I use math so intensely .. 17 years after.. But raytracing relies very much
on math.

Good idea to explain your macro. It's on my harddisk.

Regards,
Hugo

Post a reply to this message

Hugo <hua### [at] post3teledk> wrote in message news:3cad8d39@news.povray.org...
>
> Fast learning, in my honest opinion. You've got to have some programming
> experience before POV-Ray, right?
>

With people like ABX, Tor, etc. from which to learn, how long could it
possibly take to catch-on?

UGhh, I do have a little programming experience, but I don't like to think
about it. My wife took a C++ (not shur how many plusses they're up to yet)
in college about 18 months ago. On a few occasions when her work schedule
was too heavy, I had to do her assignments for her. It's a miserable
experience, I promise you, writing a C++ program when you have to figure out
how to do every single thing by looking it up in a 300 page book. It gets
even less fun when you figure out how to accomplish the task and have no
idea about the syntax or which files to include.


> Well, I started programming when I was 8 years old but it's not until
today
> I use math so intensely .. 17 years after.. But raytracing relies very
much
> on math.
>

Awesome. I'm only a couple years older and didn't even have a computer when
I was 8 years old.

Post a reply to this message