7 Replies Latest reply on Jun 4, 2007 7:53 AM by Peter Grainge

    RH6 and Peter Grainges WebHelp work round

    Phil_Wells Level 1
      I'm starting to use RoboHelp for HTML (X5.0.2) to produce multiple outputs from the same general set of source files - for example HTML Help files, WebHelp Help files and Printed training material. (I use conditional builds to control the output from the modules that I build into the master files).

      I've been using Peter Grainges work round for setting up the Webhelp Outputs. As long as all the child modules are the same level in the file hierarchy, the links work fine.

      [Note to Peter - I've got several child projects being used by more than one parent because they're at the same level in the hierarchy: your method has proved pretty flexible].

      This however, means I have to plan my file structure carefully.

      I'm using X5.0.2 at the moment. Just thought it would be prudent to check that the same work round applies in RoboHelp 6 - i.e. will the file structure I've got set up in X5.0.2 still give me the desired outputs when I get round to upgrading to RH6 - is the work round still the same?
        • 1. Re: RH6 and Peter Grainges WebHelp work round
          Peter Grainge Adobe Community Professional (Moderator)
          I am using RoboHelp 6 and the method continues to work.

          • 2. Re: RH6 and Peter Grainges WebHelp work round
            Phil_Wells Level 1
            Thanks for that Peter - I had visions of having to remake dozens of links if and when I upgrade to RH6.

            Bit of a dilemma for Adobe - if they ever sort this bug out they'll have to be careful not to foul up the hundreds of help files that have been produced using your work round.
            • 3. Re: RH6 and Peter Grainges WebHelp work round
              Peter Grainge Adobe Community Professional (Moderator)
              If they do fix the problem, it should not affect projects set up the way I describe.

              At the moment, if you put all the child projects in a folder called mergedProjects (that is, the same as the folder that gets generated by RoboHelp) then the links between parent and child would work in the output. The problem is that in the source the links from parent to child falsely report as broken so that you cannot easily see truly broken links. Thus fixing that really should not break anything.

              That said I would still carry on using this method as it does make it much easier to work.

              I notice you mentioned having a number of parent projects. I wondered why you do that as one parent should suffice unless it is to get different skins or suchlike. Not sure if you are aware the idea is to generate all the projects and then just deliver what is required. You don't need to keep compiling different configurations.

              • 4. RH6 and Peter Grainges WebHelp work round
                Phil_Wells Level 1
                Hi Peter,

                I have a number of child projects that are common to a number of help files.

                For example I havea child project called Windows_Terminology that explains what is meant by frame, radio button, scroll bar, etc. This gets included in every Help File I have. I set up SSL's for Windows_Terminology that generate outputs for Project 1, Project 2, Project 3, etc.

                I've found that as long as Windows_Terminology is at the same level in the file hierarchy as all the other child projects, then I can generate to the various 'mergedProject' sub-directories in the different help files and my single copy of Windows_Terminology sufficies for multiple projects.

                My file hierarchy is broadly as follows:

                Level 1: General type of software.
                Level 2: Module within software.
                Level 3: Master projects and general folder for child projects. (As per your structure).
                Level 4: Child projects.

                Level 1 and level 2 are primarily needed for organsation - so that files can be stored in a logical arrangement.

                Any child project in level 4 can then be put into any master project in level 3.

                As another example I have a child project called Software_Definitions. This contains definitions of the all terminology used in all our software. Outputs are controlled by conditional build tags I can output different varients for the different forms of the software we have.

                It means if a software definition is common to several forms of our software I only have to update the definition once and regenerate Software_Definitions. All the appropriate help files then get the updated definition, thus avoiding keeping individual definitions files up to date.
                • 6. Re: RH6 and Peter Grainges WebHelp work round
                  Phil_Wells Level 1
                  Yes. (We've exchanged e-mails before).

                  If you want a small working example, I can e-mail one to you.
                  • 7. Re: RH6 and Peter Grainges WebHelp work round
                    Peter Grainge Adobe Community Professional (Moderator)
                    I thought we had. Yes send me something that emulates the overall setup. Screenshots of Windows Explorer would be OK.