 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
its really nice to have some sort of manual in front of your face to flip
throught when your designing stuf...so, like, are there any books on
POV-ray? like user manuals and "POV for dummies" kinda stuff?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
DreyWerx wrote:
>
> its really nice to have some sort of manual in front of your face to flip
> throught when your designing stuf.
I find the official documentation, printed out and three-hole punched
into a notebook, is an incredible help to me. It is one of my frequent
complaints about open-source programs; they often have really poor
documentation. Fortunately, by and large, this is not the case with POV!
(I still wouldn't mind an O'Rielly on POV, though. P)
--
Dawn McKnight | "Who cares what the hipbone's connected to? I'm in Neurology!"
McK### [at] mac com | -- Justine Devlin, M.D.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
There will be a CD-ROM sold with tutorials. At least 14 people are submitting
HTML-based tutorials.
[Ugh, yes yet another plug for http://10best.raytrace.com/10best.html]
DreyWerx wrote:
> its really nice to have some sort of manual in front of your face to flip
> throught when your designing stuf...so, like, are there any books on
> POV-ray? like user manuals and "POV for dummies" kinda stuff?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
What's wrong with the povray documentation?
You can print it if you want it on paper.
Why is this phenomenon so popular? It seems that there's a rule that says
that "never read the program's own documentation; if you are in trouble,
always ask for 3rd-party tutorials in the internet".
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I think it's because we're most familiar with the
kind of documentation that MS gives us. We're
conditioned to believe that only good docs come
from 3rd party writers. And the best ones are on
the internet.
=Bob=
"Warp" <war### [at] tagpovrayorg> wrote in message
news:3a221601@news.povray.org...
: What's wrong with the povray documentation?
: You can print it if you want it on paper.
:
: Why is this phenomenon so popular? It seems that there's a rule that
says
: that "never read the program's own documentation; if you are in trouble,
: always ask for 3rd-party tutorials in the internet".
:
: --
: main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
: ):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Because example code can help make an intuitive leap that straight
documentation of syntax may not: how to actually use the syntax to get a
specific result. Manuals may or may not include example code, ( and the povray
manual includes a generous amount), but tutorials necessaily do.
Warp wrote:
> What's wrong with the povray documentation?
> You can print it if you want it on paper.
>
> Why is this phenomenon so popular? It seems that there's a rule that says
> that "never read the program's own documentation; if you are in trouble,
> always ask for 3rd-party tutorials in the internet".
>
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3A22BBC6.189ABC83@aol.com>, j charter <jrc### [at] aolcom>
wrote:
>Because example code can help make an intuitive leap that straight
>documentation of syntax may not: how to actually use the syntax to get
>a specific result. Manuals may or may not include example code, ( and
>the povray manual includes a generous amount), but tutorials
>necessaily do.
Also, manuals do not always, even when they include code, actually
include *verified* code. Even the (in my opinion wonderful) POV
documentation has had some time-wasting errors in the code examples.
(One that cost me a bit of time was an example for, I think, the
checkers pattern; their code sample "worked" because, while it was
incorrect, the two colors it appeared to choose were the two colors that
showed up--but that's because those two colors were the defaults.
Replace those two colors in the sample with any other colors, and the
defaults continued to show up. Took a while (and a post to this
newsgroup) for me to figure that one out.)
Tutorials have a tendency to discuss a single issue in depth; such an
error is unlikely to show up in a tutorial on pigment patterns, because
the tutorial would have chosen multiple colors to show how the pattern
can be changed.
(In my tutorials, I actually link each image to the exact code used to
produce that image.)
Jerry
--
http://www.hoboes.com/jerry/
"Give a man a fish and you feed him for a day. Teach him to fish, and you've
depleted the lake."--It Isn't Murder If They're Yankees
(http://www.hoboes.com/jerry/Murder/)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
j charter wrote:
> Because example code can help make an intuitive leap that straight
> documentation of syntax may not: how to actually use the syntax to get a
> specific result. Manuals may or may not include example code, ( and the povray
> manual includes a generous amount), but tutorials necessaily do.
The POV docs have a tutorial though...
--
David Fontaine <dav### [at] faricynet> ICQ 55354965
My raytracing gallery: http://davidf.faricy.net/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Someone, someday, should write one!
It would sort of be cool to see a POV book on the shelf next to ones for
3ds, Strata (the program that used to be cool - think Myst), etc.
I'd be willing to help, sample scenes, ideas, etc. :)
Yann
DreyWerx wrote:
> its really nice to have some sort of manual in front of your face to flip
> throught when your designing stuf...so, like, are there any books on
> POV-ray? like user manuals and "POV for dummies" kinda stuff?
>
>
--
--------------------------------------------------------------------
Yann Ramin atr### [at] atrustrivalieeuorg
Atrus Trivalie Productions www.redshift.com/~yramin
AIM oddatrus
Marina, CA http://profiles.yahoo.com/theatrus
IRM Developer Network Toaster Developer
SNTS Developer KLevel Developer
Electronics Hobbyist person who loves toys
Build a man a fire, and he's warm for a day.
Set a man on fire, and he'll be warm for the rest of his life.
"I'm prepared for all emergencies but totally unprepared for everyday
life."
--------------------------------------------------------------------
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Yann Ramin wrote:
>
> Someone, someday, should write one!
> It would sort of be cool to see a POV book on the shelf next to ones for
> 3ds, Strata (the program that used to be cool - think Myst), etc.
It's not that none have ever been written it's just that it has been
a while since one was written that reflects the latest version of
the program and is still in print. For titles see -
http://members.iquest.net/~cyoung/ray/
If you can read Japanese there is a recent POV-Ray book written by
a Japanese author for the Japanese POV-Ray enthusiasts. If you really
want a link to it I could probably track it down for you.
--
Ken Tyler - 1400+ POV-Ray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
