TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
> Moreover, as you note, people are human, and in the rush to meet a
deadline,
> often forget to include you in their plans. I've just recently input a
batch
> of help updates for one product based on a clearly spelled-out list of
> changes provided by one programmer before the upcoming release, but in
> reviewing these changes, discovered a batch of interface updates that were
> done over the past year without ever notifying me. So my job next week
will
> be to compare the docs line by line against the revised interface to avoid
> any embarrassments. You win some, you lose some.
Geoff replied asking me to post my response to the list:
I use the What's This Help Compiler in RoboHelp to track UI changes. That's
all I use it for.
To do this, do the following:
1. Install the application on your test machine where you will be installing
the new releases.
2. Point WTHC at that directory.
3. Select the .exe file for the application.
4. Add the dlls for the application.
5. The baseline report is run automatically.
6. When you install the new release in the same directory as the original
install,
a delta is generated
You do have to update the dll list and manage any movement of code from one
dll to another. But, you get a list of changes for each update. It's quick
and painless. And, you don't have to wait until the end to find out, or wait
for a programmer to tell you about changes.
>From Geoff's response, I would add that you can start doing this once you
get working builds or installs from development. I would reiterate that
I don't use the WTHC for anything else. I want
context sensitivity to be an index into the larger help.
Disconnected content like that generated by the WTCH is not quite
useless, but nearly so.
NEED TO PUBLISH YOUR FRAMEMAKER CONTENT ONLINE?
?Mustang? (code name) is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to Web, intranets, and online Help.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! See a live demo that
will take your breath away: http://www.ehelp.com/techwr-l3
---
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.