This content has been marked as final. Show 6 replies
this sounds like completely separate help systems shipped to you users. If so, should really consider using separate help projects. What are your reasons for managing this within a single project?
Thanks for the effort. Like I mentioned, standard modules in the application are meant for all clients, e.g. the Masters module. However, a few modules are delivered on requirement. Hence, I need to split the Help into multiple windows so I can distribute it based on which modules are shipped to a client.
I'm not sure how to manage such a Help system. Also, I shied away from multiple / merged projects because I don't know too much about it. Being the sole tech. writer for my employer, it might be daunting to update multiple projects simulatenously... so I wanted to use a single project.
Is there an alternative?? Or must I create multiple projects for one application??
Hope to hear from you or from anyone else.
I think what you need to do is use conditional build tags. You can then select which additional topics are to be included in the output.
From the user's point of view a merged set of help files is probably the best solution. Using global windows the whole help system is displayed in one window and shows only topics for the modules installed (if you can get your setup people to comply with your wishes that is ;-) ).
Handling multiple projects is not more complicated than handling a big one. Each help topic only exits in one project; if you want to create or update the help for module XYZ_1, you open project XYZ_1. If you want to edit a topic in the project Master, you open project Master. After editing a project you compile just this module and nothing else.
The only thing you have to learn are the peculiarities of the help compiler regarding merged projects. Refer to http://www.helpware.net/htmlhelp/how_to_merge.htm for a good description of these kinks.
Romeo, oh Romeo -
I suspect you may need to overcome your Fear of Merging, and read up on Merged systems in your RH help file.
It will only take a minute, and it could change your whole perspective on the problem. With each module, you can provide the corresponding help file. They will all show up in the master, as part of the TOC, just as transparently as the modules themselves.
Thanks Brian, Dirk and Roger.
Brian, I've tried conditional tags successfully before but the nature of my Help distribution makes it tedious to work with them and difficult to keep track of. Thanks anyaway for the suggestion.
Dick and Roger, you folks are potining to the same thing, multiple projects in a merged Help scenario. I will start the spadework and let you know if I hit any raodblocks on the way. Dirk, the link you provided is most helpful, to say the least.
Thanks everyone :)