Geoff Hutchison <[EMAIL PROTECTED]> writes:
> As a general comment on documentation, we're still looking for
> someone to help out with some amount of reorganization.
I'd be more motivated to create a "quick start" guide or an
"architectural overview" document, rather than reorganize the
attributes documentation.
> There was considerable discussion on breaking the documentation into
> an organization by function:
> <http://www.htdig.org/htdig3-dev/1999/02/0087.html>
Following that link...
Marjolein Katsma <[EMAIL PROTECTED]> writes:
> I just went through the whole list in attrs.html and tried to
> classify each... I'm still left with a few question marks, basically
> attributes that could fall into two groups...Two groups isn't bad by
> and of itself - it just makes it hard to decide in which separate
> file to put these attributes.
Would it be too messy to put each attribute into its own file and then
just create a variety of indexes?
If you did something similar to what you have - but grouped into files
by major function - and then had alphabetical and other indexes that
point into those files, the duplication could be handled in the index.
Theoretically only developers would care which file a particular
attribute is located in. Users would find things based on one of the
indexes.
-Tom
--
Tom Metro
Venture Logic [EMAIL PROTECTED]
Newton, MA, USA
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
