|
![](/i/fill.gif) |
Ben Chambers wrote:
> As for directories / categories / whatever you want to call them, I'd
> keep them extremely abstract and general. I'd also recommend forcing a
> separation between various component types at the top level. So, the
> directory tree might look something like this:
>
> - Textures
> -- Pigments
> -- Finishes
> -- Normals
> - Interiors
> -- Media
> - Shapes
> --Solid (CSG-able)
> --Non-solid (Non-CSG-able)
> - Functions
> -- Isosurface
> -- Positioning
> -- Other
"Charles C" wrote:
> I've checked now, and the limit for POV-Ray is 25 library_paths that you can
> add to the main POVRAY.INI. Having a lot of sub directories containing 2
> files kindof slows down browsing on one's own computer IMHO, so for some
> things some sort of a general/tidbits directory might be nice.
How about using file names with standardized multiple suffixes such as:
-- foo.texture.inc (or foo_texture.inc)
-- foo.pigment.inc (or foo_pigment.inc)
-- foo.finish.inc (or foo_finish.inc)
-- etc...
Or, if grouping *.inc files into the directory tree Ben Chambers proposes,
then within each one of these directories use standardized suffixes such
as:
-- foo.texture.skin.inc (or foo_texture_skin.inc)
-- foo.texture.stone.inc (or foo_texture_stone.inc)
-- foo.texture.wood.inc (or foo_texture_wood.inc)
-- etc...
This way, we could easily stay within the "25 library_paths" limit that
Charles C addresses.
Just thinking...
-Randall
Post a reply to this message
|
![](/i/fill.gif) |