Everything You Need To Know And How To Use Java

Everything You Need To Know And How To Use Java

Java is an object-oriented programming language developed by Sun Microsystems in the early 1990s. Java applications are designed to be compiled to by tecode, which is interpreted at runtime, unlike conventional programming languages, which either compile source code to native code or interpret source code.

The language itself borrows much syntax from C and C++ but has a simpler object model and fewer low-level facilities. JavaScript, a scripting language, shares a similar name and has similar syntax, but is not related to It is possible that some items may not make it into the release for one reason or another. Also, any API additions or other enhancements to the Java SE platform specification are subject to review and approval by the JSR 270 Expert Group. However, beyond these caveats, this list should contain the features that we are currently hoping to deliver in Java SE 6.

The desktop Java client group at Sun is working on some great features and functionality in the next release of the Java Platform, Standard Edition (Java SE, formerly known as J2SE). We thought it might be useful to detail some of the highlights here. Where possible, we will add pointers to additional information (such as bug IDs or other articles). We will also give information on the JDK 6 build into which each item is integrated as development proceeds.

It is imperative to know that the most important driver for Java Foundation Classes/Swing (JFC/Swing) technology is improving its platform look and feel — specifically, making sure that the look and feel of JFC/Swing’s Windows and GTK match the underlying platform’s look and feel.

For more information on Java SE 6 technology’s improved drag gesture recognition (the fix for 4521075), check out the entry “Improved Drag Gesture in Swing” in Shannon Hickey’s blog. For more information on the major improvements to drop support, see his blog entry “First Class Drag and Drop Support.”

In addition, where it makes sense, have Swing provide true double-buffering support. This will provide two immediate advantages: exposing a Java application (moving an application to the front that was previously obscured) will be nearly instantaneous, and an application that hangs the event dispatch thread can still have its contents restored during an expose event. For more information on this feature, check out Scott Violet’s blog.

No matter what a user has selected for desktop text settings, because there was no way for Swing to request the same behaviors as the native platform. The GTK Look and Feel for Swing already uses text antialiasing if it is a desktop setting, but it cannot request LCD text antialiasing mode. This feature addresses this issue for the native look and feel, which will automatically detect and use the desktop settings.