Hi,
There are a few java.awt.* properties that have support in the system.c
native code based on
the operating system. Most do not need to be in native code and
decoupling the code
would be a good cleanup.
I'd like to look at the properties and move the initializations to a
more appropriate place.
Since they are not used in the java.base module it would be more
appropriate for
them to be handled in the java.desktop module and the appropriate package.
At the moment, they all can be overridden by command line arguments though
in some cases, that seems to be unintentional and perhaps undesirable.
Most could dispatch on the os_name system property to select the
appropriate implementation class.
I'd like to work through this issues and see if there are any special
considerations.
Thanks for any comments and advice.
Roger
java.awt.graphicsenv: java.awt.GraphicsEnvironment.java
"sun.awt.CGraphicsEnvironment" "sun.awt.X11GraphicsEnvironment"
"sun.awt.Win32GraphicsEnvironment"
awt.toolkit : java.awt.Toolkit.java
"sun.awt.X11.XToolkit" "sun.lwawt.macosx.LWCToolkit"
"sun.awt.windows.WToolkit"
java.awt.printerjob: java.awt.print.PrinterJob.java
"sun.print.PSPrinterJob""sun.lwawt.macosx.CPrinterJob"
"sun.awt.windows.WPrinterJob"
awt.headless: This may need native code specific to the Mac.
isInAquaSession() ? NULL :"true";
sun.java2d.fontpath: sun.font.SunFontManager
The native initialization is hooked to an environment variable
"JAVA2D_FONTPATH".
Is that initialization from the environment still used or needed?
