Screen Shots

The following Screen Shots provide samples of applications that can be run in the POD Environment. Desktop Components wich are based on the Desktop Component Framework DCF and BLX are also shown. Note POD use to go by the name OCD and Some older screen shots use that name.

	User Interface CloseUps
Close up of the POD Desktop Master Tile docked in the Corner
Menus can be torn off and placed on the Desktop.
Close up view of a TileSet placed on the desktop with links to websites.
	Desktop Screen Shots
	First Screen Shot of OCD 0.1 release. Running Asteroids Applet, SwingSet JNLP App, Sticky Notes, and Desktop Tiles. The Desktop Components are created using the DCF Framework
	Screen Shot of OCD 0.2 functionality. The new Master Tile is shown with embedded TileSets and a stand alone TileSet is docked on the Edge of the Screen.
	Screen Shot of OCD 0.3. This shot shows the Editor 0.1 Application running along with the Asteroids Applet. OCD 0.3 can now be launched from a native Windows Application that sits in the System Tray.
	Screen Shot of POD 0.6. This shot shows the main POD menu torn off, some sticky notes, the NASA JTrack applet, and the FreeCell applet.
	POD 0.6.5 Running 10 instances of a Java Editor in the same VM. Because we are running all apps in the same VM they only take up 54 megs of RAM as shown in the TaskManager Window. Also after the jar resources are cached each Editor instance launches in 1 second.
	POD 0.6.5 Running 10 instances of Java SwingSet. Running all 10 instances in the same VM only takes 94 megs of RAM. Running each SwingSet in its own VM would take 650 megs of RAM. Each SwingSet instance would launch in just a few seconds but running each in its own VM causes the last several instances to take over 20 seconds to load.
	POD 0.6.5 Running 3 instances of Java SwingSet in the same VM. Each SwingSet is using a different Look and Feel even though it is running in the same VM.