This reference is purely for users viewing your page from the web. If the
plugin isn't available locally on the users machine it is downloaded
automatically from this URL. As your plugin is available locally this URL
is
ignored when the page is loaded. It's not possible to change to URL to
your
local file for your users to download; Firstly, because you're not ( I
think) licensed as a distributor of the plugin, secondly you would have to
store it on a web server for web users to have access to it.
I hope this helps.
Barry Scott
IJava UK
> ----- Original Message -----
> From: Rick L Sample <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Thursday, November 18, 1999 7:32 PM
> Subject: Fw: Re: Another newbie question
>
>
> > Thanks! I got everything working smoothly now.
> >
> > One more question though.
> > In the HTMLConverter "Options" it is pointing to
>
http://java.sun.com/products/plugin/1.2/jinstall-12-win32.cab#Version=1,2,0,
> 0
> > for the pluging. I thought when we installed the JRE1.2.2 it installed
the
> plugin?
> > Any way to point to my local copy? Where?
> >
> > Thanks!
> >
> > >>> Barry Scott <[EMAIL PROTECTED]> 11/18/99 10:11AM >>>
> > Hello all. As a Java Expert ;-) I thought I'd throw my thoughts in.
> >
> > 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
> >
> >
>
===========================================================================
> > To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
> JSP-INTEREST".
> > FAQs on JSP can be found at:
> > http://java.sun.com/products/jsp/faq.html
> > http://www.esperanto.org.nz/jsp/jspfaq.html
> >
>
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
