Ok, I've run into a lot of problems with the new SDK... 1) I did try to convert my applet HTML page with the new 1.3.1_01a HTMLConveter and it claims that no changes are needed or were made to the HTML page containing my applet tag. Since HTMLConverter doesn't seem to work, I can't tell browsers to use the new plugin.
2) I had to install the Java 3d runtime stuff by hand (well duh because I'm not getting the latest plugin because HTMLConverter doesn't work) so I still get the same wedging behavior in both Netscape 6.1 and IE 6.0. There *is* a new plugin to go along with the new SDK isn't there? That running HTMLConveter points to? And how do I get HTMLConverter to work? -- John > -----Original Message----- > From: Kyle McDonald - Eagle CAD [mailto:[EMAIL PROTECTED]] > Sent: Friday, October 26, 2001 12:03 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: [JAVA3D] jdk1.3.1_01a, IE5 and Netscape 6.1 > > > John Nelson wrote: > > > Well I guess I'm not being very clear here. Let's say I'm an applet > > developer and the only operating system that I have is Linux. > The new SDK > > isn't available for Linux, only Windows and since it's an SDK, > the upgrade > > is on the developer side NOT the runtime plugin downloaded by the user. > > > > Therefore as a Linux applet developer, I can't use it. > > > > And this is really WEIRD considering that Java is "develop once, use > > anywhere"... but Linux and Solaris folks don't even get the > "develop once" > > part. :-) Of course I'm assuming that parallel SDK's for > Linux, Solaris, > > etc will be available at some point in time. > > > > Or am I still missing something? > > > > -- John > > > John, > > As far as I know, the 'a' in 1.3.1_01a is probably some bug > fix that is only needed for Windows, and maybe even only in > the tools that come onyl with the SDK. > > However most if not all of the platforms should have a 1.3.1_01 > version available I think. Though I doubt functionality was > added in _01 bug fix release either. > > It's my impression that Mozilla, and Netscape 6.x both will > use the Java plugin for *all* applets no matter how the HTML > is written, because they don't have a JVM built in. I don't > think this is a feature that was added to the Java Plugin > at all. It's just how Mozilla and Netscape 6 are architected. > > Netscape 4 and versions of IE have a JVM that they use for > the APPLET tags and therefore need another mechanism to force > the browser to use the plugin. > > Therefore for users who are still using an older browser, if > you need your applet to run inside the Plugin JVM, you'll still > need to 'convert' your HTML. Unless you're happy with only > letting Netscape 6/Mozilla users at your applets :) > > > All that being said, I should note that while I do work for > Sun, I have really no more info on anythis than any of you do, > And I could be mistaken on what I've just said. > > -Kyle > > -- > _ > -------------------------------ooO( )Ooo------------------------------- > Kyle J. McDonald (o o) Systems Support Engineer > Sun Microsystems Inc. ||||| > High End Server Engineering [EMAIL PROTECTED] > 1 Network Drive BURL03-403 \\\// voice: (781) 442-2184 > Burlington, MA 01803 (o o) fax: (781) 442-1646 > -------------------------------ooO(_)Ooo------------------------------- > > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
