Re: Documentation [message #15046] |
Thu, 15 April 1999 00:00 |
davidf
Messages: 2866 Registered: September 1996
|
Senior Member |
|
|
Richard G. French (rfrench@wellesley.edu) writes:
> Several postings have hinted at this topic, so I thought I would raise
> the issue directly, in the hopes that we might have some effect. David
> F., you said not to get you started, and so this is my attempt to get
> you started!
I'm not taking the bait. Had you included the word "color" in
there you would have had a better chance. :-)
> What helpful suggestions can we give RSI about its documentation?
> Here is my list:
>
> 1) Enable help to be read using NETSCAPE.
Until the latest version of IDL (I think) the IDL distribution came
with an HTML version of the help files. Since this was not well
publicized, almost no one knew it was there. (Although a lot of
people complained that the IDL distribution was eating up an unbelievable
amount of their disk space with each new release.) So I think the
decision was made to NOT include it in the normal distribution.
But as I understand it, the HTML files are still available. If not
on the CD-ROM itself, then certainly from RSI. I'd poke around
their web page a bit.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting
Phone: 970-221-0438 E-Mail: davidf@dfanning.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155
|
|
|
Re: Documentation [message #15047 is a reply to message #15046] |
Thu, 15 April 1999 00:00  |
Pavel Romashkin
Messages: 166 Registered: April 1999
|
Senior Member |
|
|
"Richard G. French" wrote:
> What helpful suggestions can we give RSI about its documentation?
> Here is my list:
Hi,
Have you recently checked RSInc's web site? They are in need of people to
accomplish things like it, and with not enough people they can't go through
existing documentaiton and revamp it. I almost quit reporting
documentation bugs to them - they keep including them in future
documentation, to be published in their new releases (they like it, too, if
you report glitches fully and provide the right way to write the
documentation; I wonder if they just copy-paste bug reports in their
manuals?). Documentation in my opinion is the hardest part to create
properly. I think we should pinpoint the problems (and possibly provide
solutions, because for us it is nothing - once you located a bug, you most
likely worked around to fix it) to RSInc, because they are unable to
implement full-scale changes based on our wish lists.
Thank you,
Pavel
|
|
|