A project can have many browse sequences. They are added in the same way as just one - via the Tools > Browse Sequence Editor menu item. However they can not be excluded from the output by adding a tag. Instead if a browse sequence contains a topic from both the common and licensed help, I'd expect a licensed help user not to see the common help topic in the sequence.
You'd need to test this though. I haven't used browse sequences since my CHM file days and they work slightly differently than in WebHelp.
When you generate WebHelp, you can select which Browse Sequences are activated. Just don't select two that have a common topic as that confuses the hell out of Rh.
At one time, Rh would not let you do that but the restriction had to be removed to allow Content Categories.
See www.grainge.org for RoboHelp and Authoring tips
I'm not sure whether WebHelp and WebHelp Pro handle browse sequences differently. However, in WebHelp Pro I don't see any option for selecting different browse sequences in the Single Source Layouts > WebHelp Pro Options dialog box (Under Content, I see TOC, Index, Glossary, Variables, Language, Encoding, Default Topic, Default Window).
I created a Browse Sequence Editor for all topics. To do this, I selected the default TOC, which includes common and licensed topics, and used Auto-create using TOC. The name of the BRS is "NGP Help.brs" and it is stored at the root of the Help project.
I then tried to create four browse sequences. To do this, I navigated to the folder containing the topics for each licensed module and selected its TOC when creating the browse sequence. RH never creates another BRS. It just keeps updating NGP Help.brs.
So what I've got now is a single browse sequence that includes all the Help content, both common and licensed.
- In a licensed Help module, the browse sequence takes the user from book to book or topic to topic, even if a book or topic is not in the TOC.
- The good news is that the browse sequence in licensed module A does not take the user to a topic in licensed module B, not does it find topics in licensed module B (via Search).
Kindly let me know if I'm missing something obvious in WebHelp Pro that would enable me to create a separate browse sequence for each licensed module.
Is there a reason why you are generating WebHelp Pro now? For the record Browse Sequences don't work with WebHelp Pro.
I didn't know that Browse Sequences don't work with WebHelp Pro (nothing in the Help about this that I could see either).
When I inherited this project, the writer had set it up using WebHelp Pro because he was planning to move to the server-based RoboHelp. I have been concerned about moving to WebHelp for two reasons:
- I didn't want to break anything before we got the first product release out.
- We may move to server-based help in the future.
Before starting work on this project, my most current experience with RH was with X5!
Are there any ramifications to generating the Help as WebHelp instead of WebHelp Pro that you know of?
The “Pro” versions work with RoboHelp Server only – not just any server.
Thanks for clarifying that for the Forum, Jeff. We may move to RoboHelp Server in the future, not to just any.
Hang on, Carol
Actually Browse Sequences *are* supported in WebHelp Pro on RoboHelp Server 9. (What Colum might have meant is that you cannot select or deselect different sequences, as you can plain WebHelp). To enable them correctly, you should create a custom window (give it a unique Window name) after making WebHelp Pro your primary layout (Project Setup Pod > Windows). Then make sure the "Browse Sequence" option is ticked.
Then, when you generate the Single Source Layout, use the WebHelp Pro Options to select the Default Window you have created. You will note that unlike the plain WebHelp SSL options, there is no place to select specific browse sequences, so by default your sequence will be defined by whatever you custom-crafted in the Browse Sequence Editor.
I tested using the Employee Care Sample in RoboHelp Server 9 and it worked just fine.
Adobe Certified RoboHelp and Captivate Instructor
Me again, Carol
You also asked about the functional differences between WebHelp and WebHelp Pro, so let me elaborate.
I'm aware of only two major differences (other than the extra benefits of feedback analytics reports and management of "Areas" with authentication in RoboHelp Server).
- The behavior of Browse Sequences as explained above
- The fact that Content Categories are not supported in WebHelp Pro for this latest version 9.
As for the Browse Sequences you are trying to provide for different modules (licensed, etc.): Multiple Browse Sequences are included in a single .BRS file. The sequences are defined in the XML within the single file.
As a workaround (for either WebHelp or WebHelp Pro) you could create a NGP Help.brs. which you have already created for one module; then backup and archive it. Then, create a modification for the different module before you generate again. The NGP Help.brs. will need to have the same name as your project so you will have to manage the desired .brs file into the project folder when you generate that version. All of your other choices (TOC, Index, Conditional Tags, etc.) would remain the same for the respective modules.
Finally, I note that you are apparently generating WebHelp Pro right now even though you are not publishing it to the RH Server? This is really not the best practice. You should generate plain WebHelp for a web server that does not have RH Server on it (even though you may be getting away with it). As for your concern about "breaking" something; each output is placed in a different !SSL! folder automatically when you generate, so you should be able to generate WebHelp without interferring with the WebHelp Pro output. Then, you can re-publish to the RH Server using WebHelp Pro whenever the server is ready.
Adobe Certified RoboHelp and Captivate Instructor
Thanks for all the input. I'm printing the replies so that I can look at them tomorrow and reply thoroughly to you.
FYI, we are not publishng to a server at all. I generate the Help outputs and check them into Visual Studio Source Control. Someone in Release Engineering has written a script to get the files and install them in an IIS folder that is installed with the product.
This was all very helpful, and, for now, I've enabled browse sequences in the window.
I'll consider generating WebHelp instead of WebHelp Pro for release 2 of the product. Since I develop the Help by opening the project from Visual Studio Source Control, I need to talk to the release engineers to see if there anything might be affected by this change—there's an XML file in the Release directory in VSS but I don't know what its purpose is—there are less than two dozen context-sensitive links.
I've opened the BRS file, and so can see how it's just a series of browse sequences based on what is selected from the Available Topics list.
The only thing that I don't like—and this may require redesigning the TOCs for the licensed modules—is that pressing Next Topic or Previous Topic in a licensed module does bring up the next or previous browse sequence, which is often a common topic that is not included in that module's TOC. (The good news is that conditional build tags are honored by the browse sequences.)
Many thanks for all your help.