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.
I have a semi-related question and would like to hear your opinions on the matter. I was asked to prepare a presentation on any given subject, and my choice would be on how to create a context-sensitive *.chm file. This might be useful because the information on how to link specific topics in the CHM file to the application is scattered through the net, MSDN Library, and application help. I had to perform an extensive search to collect all information, sort through it and find out how it fits together.
Now that we are warmed up, here comes my question:
Is having a context-sensitive CHM file in the application sensible? Usable? Do you think that having a context-sensitive CHM file is in general a good idea? And would the subject be worth the trouble of everybody involved?