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