RE: Undocumenting documented features

[edunn -at- transport -dot- bombardier -dot- com]

In the case that you describe, you MUST document the older functionality. Or as
others have pointed out, direct the users to the new methods.

But I think in this case, I'd lose a lot of respect for software that had so
little care put into it that old menu items are not removed. The examples of old
functionality in software that I can think of (such as FrameMaker) do not
include easily seen menus or dialogs. Perhaps removing the functionality from
the code is a lot of work, but removing it from menus and dialogs? How difficult
can that be?

Eric L. Dunn



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com

A landmark hotel, one of America's most beautiful cities, and 
three and a half days of immersion in the state of the art:
IPCC 01, Oct. 24-27 in Santa Fe.  http://ieeepcs.org/2001/

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit 
http://www.raycomm.com/techwhirl/ for more resources and info.