----- Original Message ----- From: "John Nelson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 26, 2001 11:47 PM Subject: Re: [JAVA3D] jdk1.3.1_01a, IE5 and Netscape 6.1
> Hey Fred, > > I thought I was pretty clear. Here we go again... HTMLConverter > (in the new SDK) does nothing. Nada. IIUC, HTMLConverter _will_ do nada to a valid converted file. > Without HTMLConverter > I will have no converted applet tag. Without a converted applet > tag then how will the browser know that it needs to download the > new plugin (and which version)? I believe that with the unconverted <APPLET. . . tag the browser itself will not know. I also believe that this will be a problem to all of us who have become hardened to this issue in the recent past. But I also believe that it will be a temporary problem. I haven't pursued this, but I think that with the newly exposed version information, the applets themselves might be written to handle the issue better than the convoluted html tags. I'm confused about how this is supposed to work, and I think we need some more guidance on good practice here. I was never comfortable with the idea of 'automatic' versioning. I don't like sites that offer to do that for me, and I don't want to subject my clients and guests to it either. Especially the ones on 28.8 dialup connections. > I looked at the demos that came with the new SDK (demo/applets) > and none of them are converted. I recommended that you try the Java 3D demos. First, most have both unconverted and unconverted (*_plugin.html) launch pages. Second, running Java 3D tests whether the installer did the right thing with the ext package. If you can get deeply enough into either of those to get the Java Console up, give the Console focus and type 's'. You'll get a couple of screensful of diagnostics, much of it inscrutable, but there are a few items that identify exactly which version of the JRE you're running. This may help you verify the way that the browser installs and selects its plug-in version. As I said in my earlier message, the install of the jdk1.3.1_01a was evidently oblivious to the fact that I had installed NS6.1 with its own (1.3.1) Java support and it installed a new JavaSoft/JRE directory and left the old one intact (and, I think, the browser's plug-in setting pointing to the old one.) This is purest speculation on my part, and frankly, I'm not inclined to go back and try to reproduce it. I fixed it by deleting all of the JREs and JDKs and reinstalling. It works now, and I've become pretty skittish about changing anything (even my socks) when I get to a plateau like that. > Now I seem to recall that Paul > Pantera had said that the EMBED tag will no longer be supported > and that somehow we only need raw applet tags. And how is this a problem? > I've tried my applet with raw tags and the applet does not load > without having Java and the Java 3d runtime environments installed. True. > No prompting for plugins with raw applet tags. > > So I don't know how the new SDK is going to do the job without some > kind of conversion... and that means HTMLConverter. Hope not. > And even with the latest runtime support installed, my machine still > wedges requiring a hard reboot. Problem. Maybe there's hope with the new System info and the verbose Console setting. Disclaimer: There's not much I know for sure about this plug-in and installer business, and I understand even less about its history and intended future. I only know the things I think I saw during the install process. Other stuff is speculation. Cheers, Fred Klingener =========================================================================== 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".
