Preserve Nav pane when calling individual topic
-
- Posts: 9
- Joined: Wed Aug 21, 2013 5:33 pm
Preserve Nav pane when calling individual topic
I need the ability to navigate directly to topics with my WebHelp output. When I generate WebHelp using the "DocBook WebHelp (old)" scenario, this works properly. By properly I mean that the Nav pane with Content and Search is displayed on the left side. When I generate WebHelp using the "DocBook WebHelp" scenario, I only get the Nav pane when I call index_frames.html. The Nav pane is not displayed when I go directly to any other topic. I need to use the newer scenario. What do I need to do to get the Nav pane to display when I go directly to a topic? Thank you.
-
- Posts: 4141
- Joined: Fri Mar 28, 2003 2:12 pm
Re: Preserve Nav pane when calling individual topic
Post by sorin_ristache »
Hi,
Getting the same effect with the index_frames.html file would require you to edit the index_frames.html file and replace in the following code fragment:
the path of ch01.html with the path of your initial right-side page, for example ch02s01.html:
Regards,
Sorin
Do you mean to load the frameset version of the Webhelp output (the format of the index_frames.html file), but set any node from the Content tree as the initial page displayed in the right side content panel, instead of the default initial page (which is the first node of the Content tree)? That is not possible in the frameset version (the index_frames.html file). That is possible only in the internal frames version (the index.html file): just pass the following URL to the browser: out/webhelp/index.html#<path-to-page-from-right-side-panel>, where you replace <path-to-page-from-right-side-panel> with the relative path to the section file that you want to load in the right-side panel, relative to the out/webhelp/ directory, for example: subdir1/subdir2/mySection1.html, or mySection2.html.tuehling wrote:I need the ability to navigate directly to topics with my WebHelp output.
Getting the same effect with the index_frames.html file would require you to edit the index_frames.html file and replace in the following code fragment:
Code: Select all
function getHTMLPage(){
var currentPage = "ch01.html";
Code: Select all
function getHTMLPage(){
var currentPage = "ch02s01.html";
The left-side panel called Content should always be present in the Webhelp output, in both the internal frames version (index.html) and the frameset one (index_frames.html). Do you get the same result on one of the Docbook 5 sample documents from the default Oxygen project (the project file samples/sample.xpr opened in the Project view)? If yes, can you send us the output directory of your transformation, that is samples/docbook/v5/out/webhelp? If not, please send us a sample Docbook XML document for reproducing the problem.tuehling wrote:When I generate WebHelp using the "DocBook WebHelp" scenario, I only get the Nav pane when I call index_frames.html.
Please use the index.html version of the Webhelp output for opening the Webhelp in browser directly to a specific topic/subsection. If you must use the index_frames.html version you will need to edit the index_frames.html file as I said above.tuehling wrote:The Nav pane is not displayed when I go directly to any other topic. I need to use the newer scenario. What do I need to do to get the Nav pane to display when I go directly to a topic?
Regards,
Sorin
-
- Posts: 9
- Joined: Wed Aug 21, 2013 5:33 pm
Re: Preserve Nav pane when calling individual topic
Thank you. Using index.html#<path-to-page-from-right-side-panel> as you described works exactly as I need it to.
Also, the Nav pane DOES appear when I call index.html or index_frames.html...not sure what I was doing wrong before but I must have worked myself into a frenzy.
Also, the Nav pane DOES appear when I call index.html or index_frames.html...not sure what I was doing wrong before but I must have worked myself into a frenzy.
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service