POV-Ray : Newsgroups : povray.binaries.misc : Keyword Examples Thread Server Time
14 May 2021 03:28:20 EDT (-0400)
  Keyword Examples Thread (Message 1 to 5 of 5)  
From: Bald Eagle
Subject: Keyword Examples Thread
Date: 7 Mar 2021 22:25:00
Message: <web.604598da4b83c70f1f9dae300@news.povray.org>
Starting a new thread for updates, discussion, and piece-wise contributions.

Did a tiny bit more work on this.
I could use a quick look-over and review if there are ways to save work and make
each entry go faster.
To some extent it's going to be a tug-o-war between short-code-contest entries
and highly readable and easy to logically follow, step-wise code.

I did some easy ones to just get a few illustrative examples in, but I'd say
that maybe the entries which could use the most explanation should get
concentrated on, if at all possible.  I mean if it's trivial, we can leave it
for last, unless someone has a specific request.

And there are things that I really hardly ever "use" - aa, radiosity, focal
blurring, caustics, ...


Post a reply to this message


Attachments:
Download 'keywordexamples.zip' (10 KB)

From: Bald Eagle
Subject: Re: Keyword Examples Thread
Date: 8 Mar 2021 07:00:01
Message: <web.604610fa2e9242c31f9dae300@news.povray.org>
Morning rambling:

I can tell that just from this "simple" exercise, I will be learning a lot.

The documentation really doesn't have any information right up front about the
valid input range for most of the functions, so I always have to go looking up
the range for acos, asin, etc.

I will likely wind up revisiting the catenary to do the code example for cosh -
because it would be a nice double-duty bit of code.

Did we "know" that torus {} had its own whole set of internal csg operations?
difference, intersection, merge and union      :O
http://wiki.povray.org/content/Reference:Torus

I'm sure I will come across another handful of keywords that I had no idea were
"special" or that even existed....

The file is now 1216 lines - with only the tiniest smattering of actual
examples....  It's mostly just the list of keywords.   It makes my head hurt to
imagine conceiving it all and implementing it in source code as a functional
raytracer...

But today I have erranding so not until much later, or ... tomorrow.  ;)


Post a reply to this message

From: Ash Holsenback
Subject: Re: Keyword Examples Thread
Date: 8 Mar 2021 07:09:17
Message: <604613ed$1@news.povray.org>
On 3/8/21 6:56 AM, Bald Eagle wrote:
> Did we "know" that torus {} had its own whole set of internal csg operations?
> difference, intersection, merge and union      :O
> http://wiki.povray.org/content/Reference:Torus

http://wiki.povray.org/content/Documentation:Tutorial_Section_1#Changes_and_New_Features_Summary

under objects and object related


Post a reply to this message

From: Bald Eagle
Subject: Re: Keyword Examples Thread
Date: 3 Apr 2021 20:55:00
Message: <web.60690d7f2e9242c31f9dae3025979125@news.povray.org>
Here's the latest version, some more formatting and a few additions to the
keyword examples.

I think it would be a good idea to be able to "animate" the main file and have
the ini/clock spit out the whole list of examples.

I suppose I could just use an array of the keywords and ever so slightly adapt
what I have now...


Post a reply to this message


Attachments:
Download 'keywordexamples_0_1_0.zip' (23 KB)

From: jr
Subject: Re: Keyword Examples Thread
Date: 12 Apr 2021 03:50:00
Message: <web.6073fa7c2e9242c379819d986cde94f1@news.povray.org>
hi,

first off (to be sure, to be sure.. ;-)), I do think that the aim/goal of this
project is a very good/useful one.  (you're not alone discovering
"special"/keywords + stuff :-), so anything that aids discovery and learning is
"The Right Thing(tm)" to do imo)  however, sorry to say, as is I'm not tempted
to "pitch in", for the reasons given below.


"Bald Eagle" <cre### [at] netscapenet> wrote:
> Here's the latest version, some more formatting and a few additions to the
> keyword examples.
>
>> I did some easy ones to just get a few illustrative examples in, but I'd say
>> that maybe the entries which could use the most explanation should get
>> vconcentrated on, if at all possible.
>
>> It's mostly just the list of keywords.
>
>> It makes my head hurt to imagine conceiving it all and implementing it
>> in source code,...

unsurprising.  :-)  had a good look at this and the previous version.  over
8,000 new lines in the .pov, yet little of that is functional.

as is, your project is pretty much no-can-do.  how large is the .pov going to
grow once real(istic) content for _all_ that POV-Ray provides is furnished?
"unmaintainable" and (debug) "nightmare" come to mind.  so reason one is my
concerns regarding .. structural deficiencies.  I'd say some kind of front-end
which gives the user easy selection and spits out a .pov/.ini combo to render
the subject of interest, backed by a db where the boilerplate and other
data/info reside, would be a (much) more realistic approach.


> I think it would be a good idea to be able to "animate" the main file and have
> the ini/clock spit out the whole list of examples.
> I suppose I could just use an array of the keywords and ever so slightly adapt
> what I have now...
>
>> The documentation really doesn't have any information right up front about the
>> valid input range for most of the functions,

this brings me to the second point.  the other day I saw a _nice_ background
animation and have been pondering .. how to.  essentially, I would need to begin
by morphing a box into a stack of superellipsoid "slices".  now, in an ideal
world, I'd select superellipsoid from some list/menu and get a .pov + .ini set
which, when rendered, gives me one or more reference images (of the type you
have a knack for) showing the effect of the EW + NS "exponents" being varied by
some (selectable?) increment, so I can _see_ what my imagination cannot provide.
 therefore, reason two, what I (and perhaps others too) would look for by way of
assistance from a project like yours, I cannot see develop from the current
beginnings.  (and, honestly, has the project progressed tangibly?)

(sorry 'bout length, lacked time to make it shorter. ;-))


regards, jr.


Post a reply to this message

Copyright 2003-2021 Persistence of Vision Raytracer Pty. Ltd.