On 22 May 2001 11:45:08 -0400, Ron Parker wrote:
>On 22 May 2001 11:38:39 -0400, Warp wrote:
>>  Until you have the years of programming experience needed for this,
>>perhaps the best way is to just suggest your ideas to someone who knows
>>POV-Ray source code well and ask if he could do it.
>
>Nah, the best way is to find someone on IRC or AIM or ICQ or whatever who

Somewhat related to that, I can be found on AIM as parkrrrr just about any
time.

-- 
#macro R(L P)sphere{L F}cylinder{L P F}#end#macro P(V)merge{R(z+a z)R(-z a-z)R(a
-z-z-z a+z)torus{1F clipped_by{plane{a 0}}}translate V}#end#macro Z(a F T)merge{
P(z+a)P(z-a)R(-z-z-x a)pigment{rgbt 1}hollow interior{media{emission T}}finish{
reflection.1}}#end Z(-x-x.2y)Z(-x-x.4x)camera{location z*-10rotate x*90}

Post a reply to this message

Ron Parker <ron### [at] povrayorg> wrote:
: Nah, the best way is to find someone on IRC or AIM or ICQ or whatever who
: does know the innards but might not have the time to actually do it, and
: ask for advice whenever you get stuck.  That's how some of what's in MegaPOV
: and soon POV 3.5 got written.

  On the other hand, teaching POV-Ray patching to someone who has never
programmed before can be a much more laborious job than making the patch
yourself, so it'll be necessary to find someone who is really willing to teach
all that much... :)

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

Post a reply to this message

On 22 May 2001 11:51:58 -0400, Warp wrote:
>Ron Parker <ron### [at] povrayorg> wrote:
>: Nah, the best way is to find someone on IRC or AIM or ICQ or whatever who
>: does know the innards but might not have the time to actually do it, and
>: ask for advice whenever you get stuck.  That's how some of what's in MegaPOV
>: and soon POV 3.5 got written.
>
>  On the other hand, teaching POV-Ray patching to someone who has never
>programmed before can be a much more laborious job than making the patch
>yourself, so it'll be necessary to find someone who is really willing to teach
>all that much... :)

That's sorta why I posted my AIM nickname.  It certainly wouldn't be the 
first time I've done that sort of teaching.

-- 
#macro R(L P)sphere{L F}cylinder{L P F}#end#macro P(V)merge{R(z+a z)R(-z a-z)R(a
-z-z-z a+z)torus{1F clipped_by{plane{a 0}}}translate V}#end#macro Z(a F T)merge{
P(z+a)P(z-a)R(-z-z-x a)pigment{rgbt 1}hollow interior{media{emission T}}finish{
reflection.1}}#end Z(-x-x.2y)Z(-x-x.4x)camera{location z*-10rotate x*90}

Post a reply to this message

On 22 May 2001 11:42:59 -0400, Warp <war### [at] tagpovrayorg> wrote:

>  You mean it should be "English"?
>  I always get confused because in Finnish language names are written with
>lowercase letter (country names with capital letter, as in English). For
>example Finland (as a country) is written in Finnish as "Suomi", but
>Finnish (as language) is written "suomi" ("Finnish language" would be
>"suomen kieli").

Same in Bulgarian. However, I always capitalize the name of the nation
I belong to and the language of my ancestors, regardless of the
language I write in. It has cost me points in the past, but ****, I
kept doing it anyway :)


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

Post a reply to this message

> The syntax is the easy part. Knowing the syntax is only a very small part
> of understanding the POV source code.  Knowing the basic raytracing
> algorithm is a big part, and knowing how stuff is laid out internally
> (especially tokenize.c, parse.c, and parse.h) is a very big part.

I'll learn. :) Just let me get started somewhere... It almost sounds to me
like Warp is saying I just can't do this... or like I need years and years
to do it... Can't I at least get in the swing in a few months? I won't do
any magic, but I'll do something. That's what I mean to do. I just want to
help.

> >can help. I really do want to help make POV a better program. It's
already
> >great, but has much room for improvement.
>
> Heretic! :)

May the POV gods strike me dead if I'm blaspheming! ;)

Post a reply to this message

>   Until you have the years of programming experience needed for this,
> perhaps the best way is to just suggest your ideas to someone who knows
> POV-Ray source code well and ask if he could do it.

But I don't want to just be a passive idea-box. I want to get in there and
do some of this myself. I don't want to be remembered as "the guy who
suggested blinn shading to Nathan Kopp and gave him the link to the places
where it was explained" or anything else like that. I want a
patch/improvement I can call my own. :) And I don't want to wait a few years
to get started. I'd rather get my hands dirty quick and learn like that.

Post a reply to this message

> Somewhat related to that, I can be found
> on AIM as parkrrrr just about any time.

What if I'm on ICQ? How can I contact you then? Is there any way I could
have the best of both worlds? (Maybe this one should go to off-topic?)

Post a reply to this message

"Tony[B]" wrote:
> 
> > The syntax is the easy part. Knowing the syntax is only a very small part
> > of understanding the POV source code.  Knowing the basic raytracing
> > algorithm is a big part, and knowing how stuff is laid out internally
> > (especially tokenize.c, parse.c, and parse.h) is a very big part.
> 
> I'll learn. :) Just let me get started somewhere... It almost sounds to me
> like Warp is saying I just can't do this... or like I need years and years
> to do it... Can't I at least get in the swing in a few months? I won't do
> any magic, but I'll do something. That's what I mean to do. I just want to
> help.

I seem to recall Chris H. started doing patches not so long ago and with
little to no C or C++ experience. If Chris can do it so can you.

I say give it a shot. The worse you can do is compile something that won't
work and even if you fail you will learn a lot in the process.

-- 
Ken Tyler

Post a reply to this message

On Thu, 24 May 2001 22:27:13 -0600, Tony[B] wrote:
>>   Until you have the years of programming experience needed for this,
>> perhaps the best way is to just suggest your ideas to someone who knows
>> POV-Ray source code well and ask if he could do it.
>
>But I don't want to just be a passive idea-box. I want to get in there and
>do some of this myself. I don't want to be remembered as "the guy who
>suggested blinn shading to Nathan Kopp and gave him the link to the places
>where it was explained" or anything else like that. 

Are you saying there's something wrong with being "the guy who suggested
photon mapping to Nathan Kopp and gave him..." oh never mind.

-- 
#macro R(L P)sphere{L F}cylinder{L P F}#end#macro P(V)merge{R(z+a z)R(-z a-z)R(a
-z-z-z a+z)torus{1F clipped_by{plane{a 0}}}translate V}#end#macro Z(a F T)merge{
P(z+a)P(z-a)R(-z-z-x a)pigment{rgbt 1}hollow interior{media{emission T}}finish{
reflection.1}}#end Z(-x-x.2y)Z(-x-x.4x)camera{location z*-10rotate x*90}

Post a reply to this message

ben### [at] catholicorg (Tony[B]) wrote in <3b0dd0c5@news.povray.org>:

>May the POV gods strike me dead if I'm blaspheming! ;)

*bzap*

You have been struck by lightening.

Post a reply to this message