begin quoting Paul G. Allen as of Mon, Feb 21, 2005 at 12:22:17AM -0800: [snip] > I originally tried Sun's, but it was a version behind IBM's. that's when I
When was this? Sun has been keeping the MSWindows/Solaris/Linux versions in sync for quite some time, haven't they? > installed IBM's 1.4.1 as I needed version 1.4 and Sun only had 1.3. This > time I tried Sun first (both Sun and IBM have the same versions now it > looks like), and when that failed I tried IBM again. Huh? I'm missing something here. [snip] > Me too - very afraid, but since I am porting an application to Linux > (sounds good huh - porting a supposedly platform-independent application to > another platform - thank M$ for fsck'ing up Java) from Winsucks, I kinda > need to be able to compile under W2K (gotta make sure it works on the > original before I try it on the new :) ) I've been fortunate to have the sense of aesthetics so that it's been very easy to write platform-independent Java code; however, I've been handed Java code that was *very* platform-specific for no apparent reason other than the original author tried very hard to make it so. (Avoid JNI, use config files, don't hard-code paths or components of paths, etc. etc.) A conformant Java compiler means that it shouldn't matter which system you compile /on/ -- the resulting .class files should be byte-for-byte identical. That might be something you want to verify as well. :) > >>Under Linux I can run Java applications, I can develop Java applications, > >>I can compile Java applications and Java applets, but I can't run a Java > >>applet. > > > >Even with the AppletViewer? > > Even with appletviewer, but even if it did work, I would still need my > browser to verify operability within the actual browser. Well, first, get applets running in the appletviewer, and *then* move on to actual browsers. Restrict the variables. If it doesn't run under the appletviewer, then it's not likely that it's going to run in a browser... [snip] > >Er, why would compiling a Java applet be any different? It's the Same > >Compiler. Just a different application entry-point and delivery > >mechanism. > > Beats me, but IDEA was giving errors when configuring for an applet and > command line was having issues compiling anything (this is Winsucks, Linux > compiles fine, just no working plugin) though I did get an application to > compile. This is an example of why I don't "appreciate" IDEs. "Configuring for an applet and command-line"? Huh? Command-line entry-point is the main method. Applets (IIRC) use init. It's just a little bit of trickery to write a main() and an init() that invoke the same startup-logic -- and packaging into the appropriate .jar format is just a matter of getting the manifest right. > I'll have to try FireFox tomorrow (err, today) while I'm tootling around at > work. 'luck! -Stewart "Not impressed with GNU's cross-platform capabilities yet" Stremler -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
