This has been our experience as well - Javascript is much easier to deploy.
We currently have some Java applets that I'm working to replace with
MapBuilder because of the Java support problem in browsers. These applets
generate a constant stream of help requests: "How come the map won't show?".
The only problem I found with Javascript is if IE security settings are set
too tight to allow ActiveX controls to run, however our shop seems to be the
only place in the world that installs IE that way.
Mike
-----Original Message-----
From: geoserver-users-bounces@lists.sourceforge.net
[mailto:geoserver-users-bounces@lists.sourceforge.net] On
Behalf Of Saul Farber
Sent: June 5, 2006 6:29 PM
To: Daniel Ferreira
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Mapbuilder X Java AppletsHmm, well I'm not sure I totally agree with 2 and 3 in your
"java applet pros" column.Javascript is actually significantly easier to deploy than
java. You just put it in the <script> header on your webpage
and you're done.
Yes, browser incompatibilities are a pain, but certainly no
harder to debug than the differences in AWT semantics from
Java 1.2 to Java 1.5.