|
 |
"jr" <cre### [at] gmail com> wrote:
> am open to, and interested in, concrete suggestions to improve the photon
> documentation, wrt the "interplay" of features, and all touched on in these two
> threads; posted here or sent (pls use "helpful" subject line ;-)).
The best thing, IMHO, is for someone knowledgeable in the area, or who has the
patience and tenacity to work it out - to write a script / macro whatever -
that takes the user input and properly outputs what will happen.
An accurate flowchart is a lot better than written documentation that has to be
interpreted.
In this case where there seems to be a lot of if/then/else, then a few lines of
code is worth 10 pages of documentation that the user still has to read,
interpret, comprehend, and then implement in their own code.
Don't document it. Write the code to DO the thing. Then anyone can understand
it, or barring that, make practical use of it.
- BE
Post a reply to this message
|
|
