Autodesk 15606-011408-9300 - MAP R6.3 UPG, Developer'S Manual

Page: 40 / 208

40
|
Chapter 3 Accessing Maps
Different browsers and development environments have different assump-
tions about where the home directory is located, for example:
■
Internet Explorer
C:\windows_dir\Java\autodesk\mapguide\6.0
■ Netscape
C:\Programs\Netscape\users\ username \.autodesk\mapguide\6.0
■ Solaris
/home/ username /.autodesk/mapguide/6.0
Browser Differences with Java Edition
■ If a user with Internet Explorer requests data beyond a firewall, Autodesk
MapGuide Viewer, Java Edition fails unless the browser has already been
through proxy authorization. A simple workaround for this is to set the
browser’s home page to a site outside the firewall.
■ If a map was authored so that double-clicking a feature runs a JavaScript
command instead of opening an HTML page, the command might fail,
depending on the browser. For example, if the URL for a map feature is set
to:
javascript:alert("This is a private residence.")
users will receive an error message when they double-click that map fea-
ture in Internet Explorer. This is because different browsers support differ-
ent protocols in the Java network library (the previous example illustrates
that Internet Explorer does not support the
JavaScript
protocol in the
Java network library).
Communicating with the Plug-In from a Java
Applet
Netscape’s LiveConnect technology makes it possible to write a Java applet
that communicates with the Autodesk MapGuide Viewer Plug-In API. If you
choose to develop your application this way, you will need to know how to:
■
Access Autodesk MapGuide Viewer Plug-In from a Java applet
■ Call JavaScript functions from an Applet
The following sections cover these topics. You may also need to handle
events for Autodesk MapGuide Viewer Plug-In from your applet. For more
information about how to do this, see Chapter 5, “Handling Events.”