On Thu, 16 Nov 2000 08:20:11 -0500, Greg M. Johnson wrote:
>Q:  Am I correct that those wanting to look at a collection in the way
>Wlodzimierz is proposing would need some sort of TXT file in the
>subdirectory itself to understand the context of the files?  Or a non-html
>"povray webring-like" txt page for the whole assembly?

No. If the HTML files are reasonably clean, they can be read with any
text editor almost like plain text files. Also, if the directory names
are meaningful (e.g., "makefile.hjp" instead of "tut00043" for my (as
yet unwritten :-) tutorial on using povray with makefiles) they often give
enough clue to find a tutorial without reading the index file.

	hp

-- 


| |   | hjp### [at] wsracat      |    -- Lutz Donnerhacke in dasr.
__/   | http://www.hjp.at/ |

Post a reply to this message

On Thu, 16 Nov 2000 13:58:37 -0500, Greg M. Johnson wrote:
>The main collection "Your 10 Best Images" will have pages set up so that

Er, why is this under the Subject of "Tutorial collection"? Even if they
are on the same CD, there is no reason, why the Images section and the
tutorial section should be structured the same way.


>someone could see the thumbnails for:
> all the 3D Toons,
> all the work by Warp,
[...]
Good idea.


>Wlodzimierz ABX Skiba wrote:
>
>> if you just name subdirectories as
>> clouds1, clouds2, focblur, globals, isosrf1, isosrf2, layers, loops,
>> macro, media1, media2, pigments, plant, sky, tree1, tree2, variabls,
>> water1, water2, water3
>
>This could be done but certainly must not be the only way of locating the
>tuts. What if someone used media to make water? What if someone wrote a
>sPatch tutorial to make trees?

Set up extra index pages which group tutorials by different categories.
Or just make a big alphabetical index like they are used in books.
(Or both)

	hp

-- 


| |   | hjp### [at] wsracat      |    -- Lutz Donnerhacke in dasr.
__/   | http://www.hjp.at/ |

Post a reply to this message

On Tue, 14 Nov 2000 16:52:26 +0100, Christoph Hormann wrote:
>
>
>"Greg M. Johnson" wrote:
>> 8)  Let's adopt a common standard for differentiation between
>> explanatory text and pov code.  What should this be?  <CODE>, <PRE><TT>,
>> switch from Arial to Courier??
>
>IMO '<PRE>' and maybe a standardized syntax highlighting scheme for POV
>code would be good. 

Yes, <pre> is meant for longer code sequences. <code> can only be used
inside a paragraph and should be used for short inline code snippets.

E.g.,

    <pre>
    texture {
	pigment {
	    image_map {
		png "turm-c.png"
		map_type 2
	    }
	    scale <1, 17.5, 1>
	}
    }
    </pre>

    <p>
	In the example above, <code>map_type 2</code> is used to indicate
	cylindrical mapping.
    </p>

For visual effects (font families and sizes, colors, ...) a common style
sheet should be used.

    	hp

-- 


| |   | hjp### [at] wsracat      |    -- Lutz Donnerhacke in dasr.
__/   | http://www.hjp.at/ |

Post a reply to this message