This content has been marked as final. Show 12 replies
Welcome to the forum.
Take a look at the topic on my site about calling webhelp.
Hi blmjohnson and welcome to our community
On the outside chance that Peter's site fails to provide what you are looking for, I'll say that I may have interpreted your question a bit differently. I inferred that you are happy with what you have so far, but you simply want to add some alternate navigation without using the full TOC and whatnot.
One way you can accomplish this is by generating WebHelp two different times to two different folders with different options each time. One of the options you can use is to not use skins and opt instead for traditional WebHelp with no skin. Additionally, you would want to ensure you created a browse sequence. With a Browse Sequence and the traditional style output, your topics should end up with navigation to other topics within the topics themselves. Then you simply replace the skinned WebHelp topics that serve as CSH with the traditional WebHelp version of the same topics. You should end up with a "hybrid" system containing CSH topics that have built in navigation.
Rick, yes this is what I was lookiing for. I'll try this.
Thanks for your help.
Rick, in the last part of your response, you say you simply replace the skinned WebHelp topics that serve as CSH witht he traditional WebHelp version of the same topics.
Do you mean that I copy the mapped topics from traditional back into the skinned version.and then regenerate? Is this done in the output files under the WebHelp output folders?
sorry, I was busy with a big Release of product. Now I want to go back and check this out. I just subscribed to the RSS feed, so now I can keep up with comments.
I followed you up to the point of your last two sentences. I created the WebHelp traditional version and saw the navigation within the topics. No I want to create the hybrid you speak of and want to know how I replace the topics you mention.
The key here is to generate WebHelp two different times. Once with the skin. Once without. The one without will have the "In Topic" navigation. These need to be generated to two different folders.
After you do this, you carefully copy only the topic files from the non-skinned output and replace the topic files in the skinned output. Once you have done this, you then push it to the server. You should end up with a Skinned WebHelp system that displays topic content from a non-skinned system and has the "In topic" navigation.
Hopefully that makes better sense... Rick
I added a question on the roboengine side of things that I also subscribed to. Let me look and see specifically what it is called, but it was in response to someone else asking a question. It is a recent post. I could use your input on that as well.
Well, heck - here are the questions...
Rick, or anyone else that can answer these additional questions on RoboHelp Server 6:
Does RoboHelp server 6 work in a Server Load Balancing Environment?
Can a auto install config for a remote server be created?
Are there any licensing issues for RoboHelp server version? This means, if it is spread over many servers as well as distributing Help to customers along with the application.
Thanks in advance. These are the questions I am getting from upper management.
I used RoboEngine at a previous employer and don't remember all of these issues, but I can't proceed without answers.
I know the benefits of the server environment such as the usage reports for feedback to help improve the help system, plus the ability to have all projects published to the same location, which helps serve as a management tool.
I did see that in the RoboEngine forum. But I'm afraid I don't have much information for you. The questions you are asking are pretty technical in nature and are possibly best asked of Adobe. I might suggest contacting Adobe via This Link to ask.
Ok, thanks Rick. I'll do that. I tried asking a tech support person, but I think I need to talk to someone else within Adobe. Thanks...