Invoking A Href="link to a web page" inside ICE Browser /

Question

Hello
I would like to invoke a .
The doc says that i can use,
Popups are supported through the Oracle Help popup protocol. For example: Sheet Definition
The keyword that follows the popup protocol is a topic ID, as specified in the helpset's map file. When the pop-up link is clicked, the contents of the file associated with the topic ID is displayed in a lightweight pop-up window. For example, select this link to display a popup defined as follows: this link
Yes i tried the above. It was slick, and it showed in a LightWeight Window insider the ICE Browser. But i need an option to again browse that Light weight window that was displayed by the ICE Browser. I dont need the full functionality to work in the resulting LightWeight window, atleast i should be able to click the links ie which have <A Hrefs in the light weight window>
For instance.
The and pass the control over there. The users should be able to browse the Admin Guide if they want.
Is there any work around for this. Please advice if i am following the correct route/approach for this problem.
The platform this is needed to work are Windows/Aix. Hence is there a solution where, the webpage is displayed in the full ICE Browser viewer instead of the LightWeight viewer ?

Answer 1

It seems to me that the idea of a <wintype> should provide exactly the mechanisms that kishorekumar wants. By adding this to his map file:
<mapID target="yahoo" url="http://www.yahoo.com" wintype="external"/>
It seems to me that a proper <wintype> declaration in the helpset file would allow authors to have what Sun calls "secondary" windows in their JavaHelp application. That is, an actual JFrame object with the HTML display component and the "expected" browser navigation buttons (forward, back, print, etc.).
However, this only works if the help system is not in "docked" mode. Even then, it has one big problem in that the window containing the link is closed.
This is one aspect of OHJ that I would really like Oracle to work on. I haven't gotten around to working with this until today, but I think the wintype logic needs the following changes:
-- Links to pages with different wintypes should work even when the current window is "docked"
-- Links to pages with different wintypes should not close the current window
-- If there are multiple entries in the Map file that map a single URL to multiple wintypes (as in the example map file in the documentation), the wintype should be selected as follows:
1) If the link uses the topicid: protocol, use the wintype specified for that mapID
2) If the link uses a URL that maps to several ID's, select as follows:
1) Look for a mapID specifying the current wintype
2) Look for a mapID specifying the default wintype
3) Use the first mapID found
Jeff Beal
Ansys, Inc.