Changeset 225

Timestamp:

Dec 30, 2010, 12:44:54 AM (15 years ago)

Author:

dmik

Message:

Updated README.OS2/CHANGES.OS2 for the release.

Location:

trunk/doc

Files:

• CHANGES.OS2 (modified) (1 diff)
• README.OS2 (modified) (4 diffs)

trunk/doc/CHANGES.OS2

@@ -6 +6 @@
 
 
-1.6.0 Build 13 Alpha (2010-10-01)
+1.6.0 Build 19 Beta (2010-12-30)
+
+  - Added support for AWT and Swing classes which brings GUI capabilities.
+
+  - Lots of small fixes.
+
+
+1.6.0 Build 19 Alpha (2010-10-01)
 
   - First public release.

trunk/doc/README.OS2

@@ -1 +1 @@
 OpenJDK 6 Alpha for OS/2 and eCS
 
-Version 1.6.0 Build 13 Alpha (2010-10-01)
+Version 1.6.0 Build 19 Beta (2010-12-30)
 
-This is an alpha build intended for testing purposes.
+This is a beta build intended for testing purposes.
 
 
@@ -9 +9 @@
 INTRODUCTION
 
-This document contains a brief information on the OS/2 version of the 
+This document contains a brief information on the OS/2 version of the
 OpenJDK 6 product. Please read it carefully before starting your work.
 You may also visit the project page at
@@ -28 +28 @@
   - A OS/2 Warp 4 Fixpack 16+, OS/2 Warp 4.5 or eComStation operating system.
 
-  - Odin32 library version 0.6.21470 (2010-10-01) or above:
-  
-    ftp://ftp.netlabs.org/pub/odin/odin32bin-20101001-release.wpi
+  - Odin32 library version 0.6.21541 (2010-12-30) or above:
 
-    
+    ftp://ftp.netlabs.org/pub/odin/odin32bin-20101230-release.wpi
+
+
 
 INSTALLATION
@@ -57 +57 @@
 CURRENT LIMITATIONS
 
-  1. Only console Java applications will work! No AWT, no Swing so far.
-     This will come in a Beta.
+  1. OpenJDK will not work correctly under the OS/2 SMP kernel (Java process
+     hangs are very likely). This is a known problem of Odin32 which will be
+     addressed in further releases. The workaround is to use the OS/2 UNI or
+     Warp4 kernel instead.
+
+  2. The separate JRE package of OpenJDK is not currently available. You may
+     still extract JRE from the SDK package (it is located in the \jre
+     subdirectory of the SDK distribution archive).
+
+  3. AWT and Swing always use font anti-aliasing for all standard components.
+     If you want to disable anti-aliasing, you may use the following Java
+     command line argument:
+     
+       -Dawt.useSystemAAFontSettings=off
+
+     However, this is not recommended since Java uses standard OS/2 Type1
+     fonts by default which look really ugly with anti-aliasing turned off.
+
+  3. Some rarely used Java system classes may be still missing in this release.
 
   See the project roadmap for more information on the current progress and