TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:RE: Calling javadoc from within HTML Help From:"Richard Smith" <Richard -dot- Smith -at- windriver -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 17 Jan 2001 13:45:08 -0800
> Subject: Calling javadoc from within HTML Help
> [I] would like to be able to link to that documentation from
> within an HTML Help
> project. When I call a javadoc page from within HTML Help, it
> is displayed
> correctly, but I can't follow any of the links on the javadoc
> page (page not
> found error). Does anyone have experience doing this, or
> with linking to
> local HTML pages from within HTML Help?
While far from an expert, I've been fiddling with this lately.
The problem lies within the HTML help spec. You can only call external html
files with a fixed (i.e. not relative) path. Javadoc generates the
documentaion with relative path links. I don't know for sure, but I doubt
you can change this, since it has to do with the way java is structured,
class hierarchies=path, etc.
The exact behavior you are seeing is probably explained by the whole
relative path thing. There are some workarounds that should work which I
have not tried yet, and many things I have tried that don't work.
I've found that importing the html files into the HAT really blows. The best
way to make a CHM out of the Javadoc (if it comes to that) is by using HTML
help workshop. It will keep the javadoc .css and does the cleanest job of
any HAT for that. Then you should be able to specify a secondary window to
call the index.html file of the Javadoc generated pages contained in the
other CHM. The process for doing this might vary from one HAT to another.
I am currently using ForeHelp, so I can pass along the instructions for
diong it in forehelp if you can't find any RH specific instructions. Also,
the ehelp helpcommunity forums might be a good place to check for some howto
Develop HTML-Based Help with Macromedia Dreamweaver 4 ($100 STC Discount)
**WEST COAST LOCATIONS** San Jose (Mar 1-2), San Francisco (Apr 16-17) http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.
Sponsored by DigiPub Solutions Corp, producers of PDF 2001
Conference East, June 4-5, Baltimore/Washington D.C. area. http://www.pdfconference.com or toll-free 877/278-2131.
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.