Package org.xwt.plat

Each platform which XWT is ported to should have a subclass of Platform in this package as well as an ant buildfile.

See:
Description

Class Summary

AWT	Platform subclass for all VM's providing AWT 1.1 functionality
AWT.AWTPicture
AWT.AWTPixelBuffer
AWT.AWTSurface
Darwin
GCJ	common superclass for all platforms that use GCJ to compile a native binary
GCJ.Retainer
Java2	Platform class for most reasonable Java1.2+ Java2s
Java2.Java14Surface
Java2.Java2PixelBuffer
Java2.Java2Surface
JVM	common superclass for all platforms that run in a "real" JVM
Linux	Linux with an X11 display
PalmOS	Platform class for PalmOS devices
POSIX	Platform implementation for POSIX compliant operating systems
Solaris	Solaris with an X11 display
Win32	Platform specific code for GCJ-compiled Win32 binaries
Win32.Win32Picture
Win32.Win32PixelBuffer
Win32.Win32Surface
X11	Platform implementation for POSIX compliant operating systems with an X11 Server
X11.X11Picture	Implements a Picture.
X11.X11PixelBuffer	An X11PixelBuffer is implemented as an X11 pixmap.
X11.X11Surface	Implements a Surface as an X11 Window

Package org.xwt.plat Description

Each platform which XWT is ported to should have a subclass of Platform in this package as well as an ant buildfile.

The subclass of Platform should be named plat.java, where plat is the descriptive name for the platform. The ant buildfile should be named plat.xml, and should contain three targets:

• build: compiles all code required for the XWT Engine and creates an executable in xwt/www/html/dist/. If applicable, all debugging symbols should be left in this executable.
• run: runs the executable, loading the org.xwt.demo.main widget demo. This is useful for testing.
• dist: prepares any files required to distribute the engine (for example, a jar or cab). This step should remove debugging symbols, if applicable.

Other platform-specific files can be included in this directory, as long as they share the same filename as the main class, and differ only in extension (for example, plat.cc).

Classes in this package may subclass each other; this is useful when two classes are very similar -- they can share a superclass containing the common functionality.