This content has been marked as final. Show 2 replies
Hi John-Pierre. RoboServer can't do this on the fly. Build tags are the way to go. Just create one new tag, apply it to the topics you don't want non-franchised user to see, then apply the tag to your SSL to exclude it from the output. Viola you have your non-franchised user help. Just remove that build tag from the SSL for franchised users so they get everything. You can also create two identical WehHelp Pro SSLs - one with no build tag and the other with a build tag to avoid you having to remember to add/remove it.
How is your application going to know which help files to write? Is it a separate executable? I know it is possible for the SETUP.EXE to check for licences before installing modules but I've never gone down this line.
BTW build tags can be used on all types of output.
I was 'afraid' for this answer...
The application is just a single .exe, but there is a parameter to activate the extra module. So, when I have 2 different outputs, it means 2 different websites/folder where the help is located. When someone opens the help, the application will know which one to open based on that parameter. We plan to do the same thing with the localized versions (already did that with the .chm help where we had a file help_en.chm / help_nl.chm / help_de.chm.
By the way, I had a quick reply from adobe about the WebHelp Pro. It looks like it is going to require a different website for each help. I did not post the reply yet, because he is going to write a more detailed article.