Webhelp Classic Customizing Header
Oxygen general issues.
-
- Posts: 27
- Joined: Wed Nov 02, 2016 9:01 pm
Webhelp Classic Customizing Header
I would like to do the following customization:
1. I would like to put some icons on the header of the webhelp (classic) so that user can download pdf and chm version of the help files.
2. Also, I would like to replace the search with my own search (for example google custom search)
Can someone give me direction where I should start from and which file(s) I can customize to do this?
1. I would like to put some icons on the header of the webhelp (classic) so that user can download pdf and chm version of the help files.
2. Also, I would like to replace the search with my own search (for example google custom search)
Can someone give me direction where I should start from and which file(s) I can customize to do this?
-
- Site Admin
- Posts: 275
- Joined: Thu Dec 24, 2009 11:21 am
Re: Webhelp Classic Customizing Header
Hello,
Please find my answers below:
The XHTML fragment should contain the links to the PDF and CHM files. For example:
Note that the links use the "${oxygen-webhelp-output-dir}" macro in order to specify the paths relative to the WebHelp output directory.
You can find the procedure of including custom HTML content in your WebHelp output files at:
https://www.oxygenxml.com/doc/versions/ ... hing2.html
The PDF and CHM files and the icons for the links should be copied to the WebHelp output directory. The steps to do this can be found at:
https://www.oxygenxml.com/doc/versions/ ... urces.html
In my example the additional resources were placed in a folder named "docs" as below. The path of this folder should be configured in the transformation scenario as described in the above procedure.
You can also apply CSS styles on the generated links by contributing a custom CSS file to the WebHelp transformation.
For example:
This procedure can be found at: https://www.oxygenxml.com/doc/versions/ ... n-css.html
Please find my answers below:
You can achieve this by contributing an XHTML fragment to the transformation scenario. This fragment will be inserted in the HTML files generated by the WebHelp transformation.jojobar wrote:1. I would like to put some icons on the header of the webhelp (classic) so that user can download pdf and chm version of the help files.
The XHTML fragment should contain the links to the PDF and CHM files. For example:
Code: Select all
<div class="links">
<div class="pdf-link">
<a href="${oxygen-webhelp-output-dir}/pdf/flowers.pdf">
<img src="${oxygen-webhelp-output-dir}/pdf/pdf-icon.png"/>
</a>
</div>
<div class="chm-link">
<a href="${oxygen-webhelp-output-dir}/chm/flowers.chm">
<img src="${oxygen-webhelp-output-dir}/chm/chm-icon.png"/>
</a>
</div>
</div>
You can find the procedure of including custom HTML content in your WebHelp output files at:
https://www.oxygenxml.com/doc/versions/ ... hing2.html
The PDF and CHM files and the icons for the links should be copied to the WebHelp output directory. The steps to do this can be found at:
https://www.oxygenxml.com/doc/versions/ ... urces.html
In my example the additional resources were placed in a folder named "docs" as below. The path of this folder should be configured in the transformation scenario as described in the above procedure.
Code: Select all
docs
-- pdf
-- flowers.pdf
-- pdf-icon.png
-- chm
-- flowers.chm
-- chm-icon.png
For example:
Code: Select all
.pdf-link {
/* Add your styles here. */
}
You can read about this in our User Manual: https://www.oxygenxml.com/doc/versions/ ... earch.htmljojobar wrote:2. Also, I would like to replace the search with my own search (for example google custom search)
Alin Balasa
Software Developer
<oXygen/> XML Editor
http://www.oxygenxml.com
Software Developer
<oXygen/> XML Editor
http://www.oxygenxml.com
-
- Posts: 27
- Joined: Wed Nov 02, 2016 9:01 pm
Re: Webhelp Classic Customizing Header
Well I tried this and created the file you suggested after reading the link suggested above.alin wrote:Hello,
The XHTML fragment should contain the links to the PDF and CHM files. For example:
Note that the links use the "${oxygen-webhelp-output-dir}" macro in order to specify the paths relative to the WebHelp output directory.Code: Select all
<div class="links">
<div class="pdf-link">
<a href="${oxygen-webhelp-output-dir}/pdf/flowers.pdf">
<img src="${oxygen-webhelp-output-dir}/pdf/pdf-icon.png"/>
</a>
</div>
<div class="chm-link">
<a href="${oxygen-webhelp-output-dir}/chm/flowers.chm">
<img src="${oxygen-webhelp-output-dir}/chm/chm-icon.png"/>
</a>
</div>
</div>
You can find the procedure of including custom HTML content in your WebHelp output files at:
https://www.oxygenxml.com/doc/versions/ ... hing2.html
The PDF and CHM files and the icons for the links should be copied to the WebHelp output directory. The steps to do this can be found at:
https://www.oxygenxml.com/doc/versions/ ... urces.html
In my example the additional resources were placed in a folder named "docs" as below. The path of this folder should be configured in the transformation scenario as described in the above procedure.You can also apply CSS styles on the generated links by contributing a custom CSS file to the WebHelp transformation.Code: Select all
docs
-- flowers.pdf
-- pdf-icon.png
-- chm
-- flowers.chm
-- chm-icon.png
For example:This procedure can be found at: https://www.oxygenxml.com/doc/versions/ ... n-css.htmlCode: Select all
.pdf-link {
/* Add your styles here. */
}
1. I went to the parameters tab of the webhelp classic transformation and could not find webhelp.body.script and created a new property with this name.
2. Then I copied your code to a file and specified the file location there. After running the transformation the file content could not be found in the output.
3. I then changed the location to a url sith "file://" syntax still no joy.
-
- Site Admin
- Posts: 275
- Joined: Thu Dec 24, 2009 11:21 am
Re: Webhelp Classic Customizing Header
Hello,
First of all, the procedure described in my previous post is valid for oXygen / WebHelp Plugin 18.1.
1.
2 & 3. Indeed, the value for this parameter should be an URL. There is an error in our User Manual and will be fixed shortly.
First of all, the procedure described in my previous post is valid for oXygen / WebHelp Plugin 18.1.
1.
This means you have an older version of oXygen.... could not find webhelp.body.script and created a new property with this name.
2 & 3. Indeed, the value for this parameter should be an URL. There is an error in our User Manual and will be fixed shortly.
Alin Balasa
Software Developer
<oXygen/> XML Editor
http://www.oxygenxml.com
Software Developer
<oXygen/> XML Editor
http://www.oxygenxml.com
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