This content has been marked as final. Show 4 replies
Your developers will have to do all the heavy lifting on this one. On install, your program would identify the modules being installed and only activate the applicable folders from your complete merged help.
Thanks for your reply. It is good news that this is possible.
However, it is unclear to me how the folders and topics are activated by the developer and whether these have to be set up individually with something like Map IDs for context sensitive help through which the developers turns things on or off.
It appears from your response I can produce a single, complete WebHelp project (folder). Then the application must verify activated options and then turn those topics on/off in Help and TOC. So, I guess first question is how do they go about activating folders and if/how are the individual topics within folders handled.
If there is some resource on web or elsewhere to point me toward, I would appreciate any help there also.
For what it's worth, here is how I would understand it to work. Once upon a time, I was a lone Technical Writer working for a small vertical market software company. The software was sold in modules. Any mix of modules could be purchased. There was a gentleman there that handled maintaining the installation software. So it was his job to determine what to install via the installation software package. In this case, I would supply all the different modules and tell him which module went with which application. Then when the customer installed, only the applicable help modules were installed. There was no magic file that handled turning off or on the availability of the help. It was either present or it wasn't. If it wasn't present, then it didn't apply.
I'm guessing that this is what Leon meant.
Hopefully this makes sense... Rick
what he said...
Yes, Rick, that's what I meant. But, just in case...
To make this work, you need to identify which files belong to which modules. The way to do this is either: 1) create a project and place your topic files within folders named by module; or 2) create a project folder for each module and merge them into a single entity (use Peter Grainge's excellent method).
Then, the developers match the application's module name with the help's module name, and all is well in the land!