Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Java Plug-In/ HTML Conveter Problem

 
Nick Howell
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, my problem is that I have an applet that utilizes Swing components. Therefore, before I could upload this applet to my website, I had to run the HTML Converter on the page I was using to display it. I used the HTML converter that came packaged with the 1.4.0 J2SDK. But my problem is, when I view my webpage with IE6 (on a computer that can view the applets on java.sun.com perfectly) it requests to download the Java plug-in 1.3 when clearly it should not be doing this. What am I doing wrong? Do I need to use and older HTML Converter?
 
Nick Howell
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have done some research and I have concluded that there is actually no problem here! Yeah, so now I look stupid but this raises another problem for me. I need to make an applet that is usable by a wide range of users. I have already written it using swing. Is there a way to avoid the 5+ MB download while still allowing users to view my applet? That is how can I avoid making an applet that requires upgrading to the Java 1.3 plugin?
 
Dirk Schreckmann
Sheriff
Posts: 7023
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is there a way to avoid the 5+ MB download while still allowing users to view my applet?
The short answer is No.
The longer answer is Don't use classes that aren't part of the Java 1.1 API and you may need to compile with the target switch. Like this:
javac -target 1.1 Whatever.java
 
Nick Howell
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Not using classes that aren't in the 1.1 API...
Does that include user classes that I've made?
 
Dirk Schreckmann
Sheriff
Posts: 7023
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Of course not. Just be certain not to use any classes that were released with a Java SDK version newer than 1.1.x.
You might even want to go so far as to download the JDK 1.1 and use it to develop your applet(s).
 
Nick Howell
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks a lot Dirk. So is this a problem that all applet developers have? Will we simply have to wait several years when Java 2 is installed on the greater portion of end-users? Is there any foreseeable end to this degraded applet development?
 
Maulin Vasavada
Ranch Hand
Posts: 1873
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi Nick!
YES. there is an end to all these Applet stuff troubles....
Solution:Microsoft!!!
(They might soon remove enough support from their IE browser for java to make ppl use .NET. believe me .NET features r good but requires ur browser to BE IE and ur OS to be MS thats what i presume. i never wrote .NET application but i gather this from talks from my friend who work with .NET as much as we work with Java ...:mad

regards
maulin.
 
Dirk Schreckmann
Sheriff
Posts: 7023
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hmmm... What's simpler?
1. The customer purchases and installs Microsoft OS and uses IE and downloads 20MB .NET platform support - of course everbody would also have to buy hardware that Microsoft's software were designed for.
2. The customer uses whatever OS and browser they prefer, and installs a 10MB JRE that is free.
I'll have a... number two.
 
Dirk Schreckmann
Sheriff
Posts: 7023
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Nick Howell:
So is this a problem that all applet developers have?
Well, some have it at least. I'm sure some have customers that are running Java 2.
Will we simply have to wait several years when Java 2 is installed on the greater portion of end-users?
That seems to make sense.
Is there any foreseeable end to this degraded applet development?
Yes, I would expect that as the months and years pass by, more and more people will have Java 2 support on their systems as well as increased access to newer Java technology updates.
I wouldn't be completely surprised or frustrated by the present situation. In many cases it's not unreasonable to point the user to the JRE download if they don't already have Java 2 installed. For a long time, visual basic developers had to deal with users not having one dll package or another installed (and I doubt that they don't have to deal with that even today).
Sure, for the developer it'd be nice if users were always up to date on the latest technologies, but that's just not the case for all users. I recently worked in an office that was still based on a Windows For Workgroups 3.11 network and they were using the old WordPerfect and probably the first version of FoxPro ever created.
 
Nick Howell
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks guys! I think I'm gonna have to stick with Java (Fight the power! ). I don't particulary like the idea of having to spend 1000 odd dollars to use some mediocre (I've developed with Visual Studio before and it's not THAT great!) program that helps support monopoly and deters technological advancement! Maybe I'll just have to make this applet so incredibly desirable that user's with 14k connections will be willing to wait hours to download Java 2 just so they can use my applet! Yeah, that's the ticket! Thanks again.
-Nick
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic