Whoa!
Being so smart I got it wrong! :-)
____________________________________
You can run both Swing packages together but the
import statement would need
to be fixed before deployment. If the intended audience will use the plug-in
the import statement should be:
import javax.swing.*;
to be fixed before deployment. If the intended audience will use the plug-in
the import statement should be:
import javax.swing.*;
If the audience are going to use Swing1.0.1 the
statement should be:
import com.sun.java.swing.*;
____________________________________
Barry Scott
IJava
----- Original Message -----
From: Barry Scott <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 18, 1999 4:11
PM
Subject: Fw: Re: Another newbie
question
>
> Firstly -
>
> The demo\jfc\swingset samples : it appears Sun has missed something out in
> the SwingSetApplet.html file :-o.
>
> The line
> <applet code=SwingSetApplet width=695 height=525>
>
> should read :
> <applet code=SwingSetApplet width=695 height=525 ARCHIVE=SwingSet.jar>
>
> If you follow Sun's advice about putting the SwingSet.jar file in the
> CLASSPATH, you could find youself developing solutions that don't work on
> your clients' machines.
>
> Secondly -
>
> Microsoft has no intention of supporting Java2 in IE and Netscape is
> currently even worse. The only way to use Java2 centric classes in the
> context of the browser is to use the plug-in. If you've been studying your
> JSP properly you'll find it has a tag that automatically generates the HTML
> code required to load the plug-in.
>
> The tag is :
> <jsp:plugin>
>
> Thirdly -
>
> You have to be careful which versions of the JDK you develop and test with
> as the name of the swing package was changed in 1.2. The old package was
> com.sun.java.swing and the new one is javax.swing. If you write a swing app
> in 1.1 it won't run in 1.2 without adjustment and the same the other way.
> ALSO if you have two copies of the JDK on your system, say 1.1.8 and 1.2.2
> and the PATH variable points to the OLD appletviewer, trying to run a 1.2
> applet with:
>
> AppletViewer myAppletPage.html
>
> won't work without adjustment.
>
> You can run both Swing packages together but the import statement would need
> to be fixed before deployment. If the intended audience will use the plug-in
> the import statement should be:
> import com.sun.java.swing.*;
>
> If the audience are going to use Swing1.0.1 the statement should be:
> import javax.swing.*;
>
> The easiest way to deploy the app for any audience is to bundle the swing
> package you use for development.
>
> OK? Any Questions? ;-)
>
> Barry Scott
> IJava UK
>