As reported earlier Java 6 is not on Leopard. The default Java is 1.5.0_13.
Swing in Tiger used Cocoa-based widgets, Swing in Leopard doesn't so a bunch of stuff doesn't look as nice. In addition Apple removed all copies of the Java 6 Developer Seed from the Apple Developer Connection -- presumably because it doesn't work with Leopard. I expect an optional download for Java 6 on Leopard within a month or two -- however I have nothing like hard info for this prediction. If you are using a Java 6 preview release on Tiger make sure you switch to Java 5 before upgrading to Leopard. See this email: Saturday Oct 27 Mike Swingler, Java Frameworks Engineer at Apple Inc. wrote: >I'm sorry, but if you have a Java 6 installation on your machine as a result >of upgrading from Tiger with a Developer Preview installed, it does not work >on Leopard due to to binary incompatibility. > >We have been able to replicate this failure, and unfortunately it affects Java >Preferences and Web Start. If you also had Java 6 specified as your preferred >Java Application Runtime in Java Preferences, this now also breaks >/usr/bin/java and the related tools on the command line. > >If you remove or move aside the >/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0 >directory, as well as the "1.6" symlink in "Versions", that should restore >your Java installation on Leopard to a working state. > >We normally do not advise tinkering with the internals of the >JavaVM.framework, however in this instance, it does appear to be necessary. > >Our sincerest apologies for this oversight, >Mike Swingler >Java Frameworks Engineer >Apple Inc. Fonts in Java also look worse. Here's the explanation: >Fonts are now rendered using the Sun 2D graphics pipeline instead of the >Quartz pipeline. Unfortunately, the font rendering system in Sun's 2D pipeline >in Java 5 does not have the concept of LCD-antialiased glyphs, so we can only >show "grey bits". If this is a significant issue for you, you can try >launching your application with the "apple.awt.graphics.UseQuartz" system >property set to "true". > >The Quartz pipeline is also automatically used for printing, and applications >run with a User Interface Scale Factor > 1.0 (aka resolution independence). > >Quartz is not used for rendering into on-screen windows or BufferedImages by >default, unless Quartz has been enabled for your application. This is a change >in the default behavior between Java on Tiger, and Java on Leopard. On Tiger, >the default was that Quartz was on, unless you specifically turned it off to >request the Sun 2D graphics pipeline. > >If you open the Quartz Debug tool (at /Developer/Applications/ Performance >Tools/Quartz Debug.app) and choose "Show User Interface Resolution" from the >"Tools" menu, you can adjust the scale factor the windows and controls in >newly launched applications. > >This is currently a developer-only feature for Leopard, but we are interested >in hearing about what works and what doesn't. One of the unique side effects >on Java applications is that we cannot use the Sun 2D graphics pipeline in >this mode, because it is designed with the concept of 1 pixel == 1 point. >Quartz has a bit more flexibility in this regard, so we automatically switch >over to it in applications that have a scale factor that is not 1.0 pixels per >point. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
