Thanks for the info, but the docs for sup 3.1e are not complete.
I have mega on another PC and had not looked there, though......

David Wilkinson wrote:

> On 14 Feb 2000 16:55:33 -0500, ron### [at] povrayorg (Ron Parker) wrote:
>
> >On Mon, 14 Feb 2000 15:24:56 -0500, Greg M. Johnson wrote:
> >>> The docs for superpatch do not give any syntax at all on how to use
> >>> the named functions as functions in isosurfaces.
>
> >
> >In case you can't look it up (but you should, because it's a useful
> >thread) here's the syntax that works for me for the sphere function:
> >
> >isosurface {  function { "Sphere" <1> }  pigment { color red 1}}
> >
>
> You just beat me to the punch Ron :-)
>
> The docs for MegaPov give the correct syntax for the named isosurface functions, but
> MegaPov also requires
>  contained_by {}
>  in the isosurface definition.
>
> e.g.
>
> isosurface {  function  { "rounded_box" <.2> }
>    contained_by { }
>     pigment { Red}
> }
>
> In testing this with MegaPov I found a bug has been added since SuperPatch.
> The size of the rounded box is determined by the size of  contained_by !
> With no value for contained_by you get a rounded box of unit sides. But;
> contained_by { box {0,4}}
> makes the rounded box of sides 4!
>
> Ah well, it just goes to keep us on our toes :-)
> ----------------------------
> dav### [at] cwcomnet
> http://www.hamiltonite.mcmail.com
> ----------------------------

Post a reply to this message

On Tue, 15 Feb 2000 07:14:48 -0500, "Greg M. Johnson"
<gre### [at] my-dejanewscom> wrote:

>Thanks for the info, but the docs for sup 3.1e are not complete.
>I have mega on another PC and had not looked there, though......
>
He he he, the docs have never been complete for any POV version that
I've used. That is, if you compare it to some commercial software that
comes with a thick, well written tutorial on how to use the product
and all its features. Of course, we don't have to pay a large price
for POV-Ray, like some of those commercial applicaions with their
thick manuals.   :)

I understand that the programmers are busy enough just writing the
software. I also don't mind "reading between the lines" a little bit,
if it means the developers get to spend more time perfecting the
software. I guess in a perfect world, some talented person would be
appointed the official technical writer for the POV-Team. I'm thinking
of someone who doesn't write any actual code, but spends their time
documenting  what the programmers have done.

Just a thought...

Post a reply to this message

Yes, I know to some degree, I'm an ungrateful whiner.

BUT, there are places where keywords are described with simply the words
"This goes with that."

I just think that with a tiny bit more effort, just one working example of
every concept could be added to the docs.

Glen Berry wrote:

> On Tue, 15 Feb 2000 07:14:48 -0500, "Greg M. Johnson"
> <gre### [at] my-dejanewscom> wrote:
>
> >
> He he he, the docs have never been complete for any POV version that
> I've used. That is, if you compare it to some commercial software that
> comes with a thick, well written tutorial on how to use the product
> and all its features. Of course, we don't have to pay a large price
> for POV-Ray, like some of those commercial applicaions with their
> thick manuals.   :)
>

Post a reply to this message

On Wed, 16 Feb 2000 10:15:10 -0500, Greg M. Johnson wrote:
>BUT, there are places where keywords are described with simply the words
>"This goes with that."

Examples?

>I just think that with a tiny bit more effort, just one working example of
>every concept could be added to the docs.

So stop whining about it and DO IT!  That's how I got to be the superpatch
guy in the first place, I stopped whining about the fact that there were so
many different patches and I did something about it.

-- 
These are my opinions.  I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html

Post a reply to this message

Greg M. Johnson wrote:
>> The docs for superpatch do not give any syntax at all on how to use
>> the
>> named functions as functions in isosurfaces.

On 2000/01/27 Y.Tanabe posted two example scene files in this group, 
containing all the functions of i_nfunc and I_algbr.

Message-ID: <388FB2B5.9A9D7483@kh.rim.or.jp>
Message-ID: <3890665D.815A92CE@kh.rim.or.jp>

Ingo

-- 
Photography: http://members.home.nl/ingoogni/
Pov-Ray    : http://members.home.nl/seed7/

Post a reply to this message

On 16 Feb 2000 10:28:31 -0500, ron### [at] povrayorg (Ron Parker)
wrote:

>On Wed, 16 Feb 2000 10:15:10 -0500, Greg M. Johnson wrote:
>>BUT, there are places where keywords are described with simply the words
>>"This goes with that."
>
>Examples?
>
>>I just think that with a tiny bit more effort, just one working example of
>>every concept could be added to the docs.
>
>So stop whining about it and DO IT!  That's how I got to be the superpatch
>guy in the first place, I stopped whining about the fact that there were so
>many different patches and I did something about it.

I can't program well enough to help with that aspect of POV, but
perhaps I could help with the docs a bit - maybe make an unofficial
supplement or tutorial of some sort. I had actually thought of making
a supplement in the past, and now I'd like to give it a try.

Attention Greg: 
Give me some specific examples of topics that you personally feel are
in need of  elaboration and I'll start from there. (Anyone else is
welcome to make suggestions as well.)

later,
Glen Berry

Post a reply to this message

Ron Parker wrote:

> So stop whining about it and DO IT!  That's how I got to be
> the superpatch guy in the first place, I stopped whining about
> the fact that there were so many different patches and I did
> something about it.

You mean ordinary mortals like me can actually make suggestions for specific
text to go into next docs? I'm honored! I do not expect a user's manual like I
got for Animation:Master, just working examples of every feature.


> On Wed, 16 Feb 2000 10:15:10 -0500, Greg M. Johnson wrote:
> >BUT, there are places where keywords are described with simply the words
> >"This goes with that."
>
> Examples?

1. Quotes around library names in isosurfaces in sup.
2. Reflection in sup.
3. Definition of media terms like lambda in 3.1e. (This inspired my "this goes
with that" slur.)

Again, I greatly appreciate the gift to the world that the pov and patch teams
have offered.  If mortals can in fact write up doc modifications, I will get to
work! 8-))

Post a reply to this message

"Greg M. Johnson" wrote:
> 
> Ron Parker wrote:
> 
> > So stop whining about it and DO IT!  That's how I got to be
> > the superpatch guy in the first place, I stopped whining about
> > the fact that there were so many different patches and I did
> > something about it.
> 
> You mean ordinary mortals like me can actually make suggestions for specific
> text to go into next docs? I'm honored! I do not expect a user's manual like I
> got for Animation:Master, just working examples of every feature.
> 
> > On Wed, 16 Feb 2000 10:15:10 -0500, Greg M. Johnson wrote:
> > >BUT, there are places where keywords are described with simply the words
> > >"This goes with that."
> >
> > Examples?
> 
> 1. Quotes around library names in isosurfaces in sup.
> 2. Reflection in sup.
> 3. Definition of media terms like lambda in 3.1e. (This inspired my "this goes
> with that" slur.)
> 
> Again, I greatly appreciate the gift to the world that the pov and patch teams
> have offered.  If mortals can in fact write up doc modifications, I will get to
> work! 8-))

As a TAG member I would be willing to take any submissions you may have to
the docs and make sure that the appropriate POV-Team members recieve and
review them. Any examples you may have of a new feature that you think is
better than the existing examples would also be welcome.

You can send this material to ken### [at] tagpovrayorg or any of the other
TAG members for that matter.

-- 
Ken Tyler -  1300+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/

Post a reply to this message

Greg M. Johnson <gre### [at] my-dejanewscom> wrote...
>
> You mean ordinary mortals like me can actually make suggestions for
specific
> text to go into next docs? I'm honored! I do not expect a user's manual
like I
> got for Animation:Master, just working examples of every feature.
>

I'll take submissions for MegaPov doc updates.  If they're in HTML and
follow the format of the existing Docs, that would be especially helpful.
Also, if Ken and the other TAG members want to help with MegaPov docs,
they're welcome to do that as well.  :-)

-Nathan

Post a reply to this message

Greg M. Johnson <gre### [at] my-dejanewscom> wrote:
: You mean ordinary mortals like me can actually make suggestions for specific
: text to go into next docs? I'm honored!

  AFAIK povray is made entirely by "ordinary mortals" like you or me.
  Every suggestion and contribution is valuable. Remember that povray is made
entirely by volunteers.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message