"Charles C" <nomail@nomail> wrote:
> I think it all depends on what we're building here.  Something like a
> professonal product containing the best of the best, or a community effort
> containing some things that might not be as up-to-snuff as others.
> ...
> I'd lean more towards guidelines, and tutorials on how to make #includes
> "nice," kinda like what Chris B was talking about.

Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> Have two sections of the library: the 'standard', and the 'ad-hoc' one.
> Everything goes into 'ad-hoc' to start with, until an administrator checks
> it. If it meets the standard, it goes into the standard area.

I like the direction in which this discussion is heading.

My personal preference is for #macro includes with a parameter each for size
or texture-density where appropriate.  I just got done rewriting my personal
includes, eliminating all #declares.  My headers now have two new lines:

// Manifest: #macro_1, #macro_2, ...
// Dependencies: "file_1.inc", "file_2.inc", ...

BTW: I'm more of a hands-on learner.  So, this exercise served to inform me
better in participating in this discussion.  It is not my intention to
promote my personal standard.  I share it only as an example.

I would still like to promote my "scene ruler" #macro-generated objects for
use by the 'ad-hoccers' who want to make their textures and such available
via #declares (assuming we do end up with an 'ad-hoc' area).

Also, I'd be happy to help with the tutorials.

-Randall

Post a reply to this message