Skip to main content

Question about OBJECT tag

4 replies [Last post]
Anonymous

Could really use some insight on this problem I'm having.

Anyone out there using OBJECT tag in their online help?
I've used it in the past and it's worked great but something's
happened in the last month and it is broken when the helpviewer
is run in a Windows environment.

I use LinkLabel as the viewerActivator, supply text to the name param
and the path to the linked file for the content param. In the Solaris
environment, the helpviewer shows the page containing the OBJECT
tag with the active text in blue. Clicking on the text opens
the secondary window that displays the linked page. Correct behavior
which used to occur as well when running on Windows.

However, since March, the helpviewer, when run on Windows, displays
the page containing the OBJECT tag with a gray button gif. No active
text appears on the page. Clicking on the button opens
a secondary window but all you see is the window title. You have
to manually stretch the window open and the page displayed is the
same page containing the OBJECT tag.

I can't figure out why the helpviewer doesn't display correctly
anymore on Windows. I've tried using an older version of javahelp
(am currently using 2.0_04), tried displaying an old helpset, have
rechecked the tag definition, and I get proper behavior on Solaris
and broken behavior on Windows in every instance. I can't figure
out why the sudden problem on Windows (both XP and Win2000).

Has anyone else run into this?

--jo lawless
Sun Microsystems, Inc.

********************************************************************************

You may leave the list at any time by sending message with no subject and
"SIGNOFF JAVAHELP-INTEREST" in the body to LISTSERV@JAVA.SUN.COM. Archives
are available at http://archives.java.sun.com/archives/javahelp-interest.html.
Submit bug reports at http://java.sun.com/cgi-bin/bugreport.cgi.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Paul Fussell

Jo,

Could you email the actual object tag? For example, the following tag
that shows a popup window in the NeBeans visual web help works fine
in Windows XP:

If I change the viewerStyle to javax.help.SecondaryWindow, that works as well.

--Paul

At 02:56 PM 4/3/2007, Jo Lawless wrote:
>Could really use some insight on this problem I'm having.
>
>Anyone out there using OBJECT tag in their online help?
>I've used it in the past and it's worked great but something's
>happened in the last month and it is broken when the helpviewer
>is run in a Windows environment.
>
>I use LinkLabel as the viewerActivator, supply text to the name param
>and the path to the linked file for the content param. In the Solaris
>environment, the helpviewer shows the page containing the OBJECT
>tag with the active text in blue. Clicking on the text opens
>the secondary window that displays the linked page. Correct behavior
>which used to occur as well when running on Windows.
>
>However, since March, the helpviewer, when run on Windows, displays
>the page containing the OBJECT tag with a gray button gif. No active
>text appears on the page. Clicking on the button opens
>a secondary window but all you see is the window title. You have
>to manually stretch the window open and the page displayed is the
>same page containing the OBJECT tag.
>
>I can't figure out why the helpviewer doesn't display correctly
>anymore on Windows. I've tried using an older version of javahelp
>(am currently using 2.0_04), tried displaying an old helpset, have
>rechecked the tag definition, and I get proper behavior on Solaris
>and broken behavior on Windows in every instance. I can't figure
>out why the sudden problem on Windows (both XP and Win2000).
>
>Has anyone else run into this?
>
>--jo lawless
>Sun Microsystems, Inc.
>
>********************************************************************************
>
>You may leave the list at any time by sending message with no subject and
>"SIGNOFF JAVAHELP-INTEREST" in the body to LISTSERV@JAVA.SUN.COM. Archives
>are available at http://archives.java.sun.com/archives/javahelp-interest.html.
>Submit bug reports at http://java.sun.com/cgi-bin/bugreport.cgi.

********************************************************************************

You may leave the list at any time by sending message with no subject and
"SIGNOFF JAVAHELP-INTEREST" in the body to LISTSERV@JAVA.SUN.COM. Archives
are available at http://archives.java.sun.com/archives/javahelp-interest.html.
Submit bug reports at http://java.sun.com/cgi-bin/bugreport.cgi.

Jo Lawless

Thanks bunches guys,

Here's one of my files with the object tag and the file
that is linked to it.

Note that the DOCTYPE header is for xhtml 1.0 transitional,
per Roger this shouldn't affect Javhelp. In any case, I've
tried displaying this very file using the old html 3.2 doctype
header and get the same problem on Windows.

--jo

********************************************************************************

You may leave the list at any time by sending message with no subject and
"SIGNOFF JAVAHELP-INTEREST" in the body to LISTSERV@JAVA.SUN.COM. Archives
are available at http://archives.java.sun.com/archives/javahelp-interest.html.
Submit bug reports at http://java.sun.com/cgi-bin/bugreport.cgi.
[att1.html]
[att1.html]

Paul Fussell

I can't duplicate your problem. I did notice when I opened your file
in DreamWeaver that it insisted on adding a bunch of "/>" closing
tags to the params and a few other tags, which was due to the XHMTL
doctype header. So, a couple of things you might want to try:
- Use /> to close off your tags if the XHMTL doctype is important.
- I know you've said that you changed the header and it didn't help.
We're using the following one: HTML 4.01 Transitional//EN">

Also, are these files being displayed in the JavaHelp viewer? If so,
what version of Java SE are you using?

Does the software run in the NetBeans environment?

--Paul

At 03:50 PM 4/3/2007, Jo Lawless wrote:
>Thanks bunches guys,
>
>Here's one of my files with the object tag and the file
>that is linked to it.
>
>Note that the DOCTYPE header is for xhtml 1.0 transitional,
>per Roger this shouldn't affect Javhelp. In any case, I've
>tried displaying this very file using the old html 3.2 doctype
>header and get the same problem on Windows.
>
>
>--jo
>
>********************************************************************************
>
>You may leave the list at any time by sending message with no subject and
>"SIGNOFF JAVAHELP-INTEREST" in the body to LISTSERV@JAVA.SUN.COM. Archives
>are available at http://archives.java.sun.com/archives/javahelp-interest.html.
>Submit bug reports at http://java.sun.com/cgi-bin/bugreport.cgi.
>
>
>
>Adding Devices
>
>
>
>No devices are provided by the Content Delivery Server. You must add
>or import devices. An XML file of the device definitions is created
>for you when you add a new device. Existing devices can be imported
>directly into the Content Delivery Server, see
>Importing Devices.
>
>[]
>To add a device, follow these steps:
> * Click Devices in the main menu.
> * Click New Device.
> * Specify the . Asterisks (*) indicate required fields.
> * Note for MicroEdition-Configuration and MicroEdition-Profile,
> you must select all applicable libraries. For example, if you have
> content that supports CLDC 1.0 and content that supports CLDC 1.1,
> you must select both libraries so that content supporting each
> library runs on the device. If the Push Type is SMS, you must also
> select an SMS delivery type. You can choose NSM, EMS, or None.
> * Click Create New Device.
> * The Device Management page opens displaying the properties of
> the new device. A device definitions XML file is created for the
> device. You can click on the device name in the list of devices and
> click Export to see the contents of the file.
> * Click OK.
> * The Device Management page opens displaying the list of devices.
>
>Once the new device is added, you also need to configure the
>device's MIME type mappings, see Mapping MIME
>Types to Devices.
>
>Related tasks:Importing Devices
><../../daily/devices/view-devices.htm>Viewing Devices
><../../daily/devices/examine-device.htm>Examing Device Definitions
>Setting a Default Device
><../../daily/devices/activate-device.htm>Activating New or
>Quarantined Devices <../../daily/devices/edit-device.htm>Editing
>Device Capabilities <../../daily/devices/delete-device.htm>Deleting
>Devices <../../daily/devices/export-device.htm>Exporting Devices
>----------
><../../credits.htm>Legal Notices
>********************************************************************************
>
>
>You may leave the list at any time by sending message with no
>subject and "SIGNOFF JAVAHELP-INTEREST" in the body to
>LISTSERV@JAVA.SUN.COM. Archives are available at
>http://archives.java.sun.com/archives/javahelp-interest.html. Submit
>bug reports at http://java.sun.com/cgi-bin/bugreport.cgi.
>
>Adding a Device Fields
>
>
>
>Field Description
>Name The device name.
>Description A device description. Maximum 256 characters.
>Manuafacturer The manufacturer's name.
>Manuafacturer Number The manufacturer's model number.
>User-agent The user-agent is a regular expression that contains
>information about the device, such as hardware, browser, and model
>information. Specifying the user-agent enables the Content Delivery
>Server to identify the device without having to ask the subscriber
>to specify the device details.
>
>Enter a unique identifier for the mobile device. The regular
>expression must match the entire user-agent expression given by the
>device. You can specify wildcards in the string as .* but be careful
>where you place it.
>
>For example, if the user-agent from a device is
>SAMSUNG-SGH-E700-OLYMPIC2004/1.0 UP.Browser/6.1.0.6 (GUI) MMP/1.0
>(Browser WAP Proxy/1.0), the user-agent regular expression pattern,
>SAMSUNG-SGH-E700.*, matches it. The expressions, SAMSUNG-SGH-E700
>and .*SAMSUNG-SGH-E700, do not match as they only partially match
>the user-agent coming from the device.
>Supported Libraries A set of APIs supported by the device.
>
>Select the libraries that the device supports. To select multiple
>libraries, hold the Control key down and click the libraries with
>the left mouse button. Selected libraries are highlighted.
>Browser Type Select the type of browser supported by the device.
>
>If not specified, a default XHTML or WML browser is used. If you do
>not see the browser type you need, update the browser.config file in
>$CDS_HOME/deployment/deployment-name/conf. For information on how to
>add new browser templates, see the "Device-Specific User Interface
>Framework" chapter in the Integration Guide.
>Device Capabilities Enter the system, browser, user interface,
>software, mandatory, and Content Delivery Server-specific
>capabilities of the device. Specify these capabilities as needed.
>See for details and example values.
>
>----------
><../../credits.htm>Legal Notices
>********************************************************************************
>
>
>You may leave the list at any time by sending message with no
>subject and "SIGNOFF JAVAHELP-INTEREST" in the body to
>LISTSERV@JAVA.SUN.COM. Archives are available at
>http://archives.java.sun.com/archives/javahelp-interest.html. Submit
>bug reports at http://java.sun.com/cgi-bin/bugreport.cgi.

********************************************************************************

You may leave the list at any time by sending message with no subject and
"SIGNOFF JAVAHELP-INTEREST" in the body to LISTSERV@JAVA.SUN.COM. Archives
are available at http://archives.java.sun.com/archives/javahelp-interest.html.
Submit bug reports at http://java.sun.com/cgi-bin/bugreport.cgi.

Jo Lawless

Hi Paul,

Larry came over and spent about an hour and half trying
to figure it out. We think now the problem lies with the
javahelp that I downloaded from java.net. Either something
got messed up in the download (I put it in my old jh2.0
directory thinking new files would be added, existing files
of the same name would be replaced) or there might be
something wrong in one of the javahelp files.

Larry couldn't reproduce the problem on his system either but
he was going nuts trying to figure out why things were
screwy on my system. I'm removing the jh2.0_04 I currently
have installed and will do a clean install from java.net
and see how that goes. Unfortunately, I can't get to the
site right now. It keeps timing out.

The >s that show are due to trying to close img tags and
the link tag by using the shortcut, />. JEditorPane reads
that as a special character so I'll have to use
and

and I think the link tag is required to be closed
even in xhtml.

Thanks for the help, I'll let you know what happens.

--jo

********************************************************************************

You may leave the list at any time by sending message with no subject and
"SIGNOFF JAVAHELP-INTEREST" in the body to LISTSERV@JAVA.SUN.COM. Archives
are available at http://archives.java.sun.com/archives/javahelp-interest.html.
Submit bug reports at http://java.sun.com/cgi-bin/bugreport.cgi.