Stephen Turner wrote:
> I'm trying to think how to document this better. I don't think just a list
> of configuration commands is the answer though. There are a couple of
> hundred of them, and they can be used in different ways so it would require
> several hundred lines to do it that way.
>From the first day I started using Analog I said "Where's the reference
section?". Then a couple weeks into using it I stubbled over the index (which is
obvious, I just wasn't looking) and that seemed to do ok. However, (and maybe
this is just cause I've been programming for so long I've trained myself to
learn from references :) it would be handy (and a hell of a project) to develop
a reference for all the commands. That is each specific command is listed with a
description, usage examples, and discussion of how it affects the ouput.
But, then, maybe that's just me.
--
Jeremy Wadsack
OutQuest Magazine
a Wadsack-Allen publication
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
