Package com.partnersoft.preferences.model

End-user preferences data models.

See:
Description

Interface Summary

SubsystemPreferences

Interface for all subsystem-specific preference model objects.

Class Summary

AbstractSubsystemPreferences	Starter implementation for the SubsystemPreferences interface.
ControlPreferences	Preferences for map control behavior.
GraphicsPreferences	SubsystemPreferences for graphics settings, including both Java2D/AWT settings and map rendering settings.
Java2dPreferences	Specific preferences controlling Java2D rendering behavior.
LayoutPreferences	Preference settings controlling Map Viewer application layout and GUI behavior.
MapsetPreferences	SubsystemPreferences for map control behavior.
MapSpacePreferences	Preference settings for map spaces - primarily serves as the container for per-mapset preferences.
OpenglPreferences	Preferences for OpenGL rendering engine.
SoundPreferences	SubsystemPreferences for sound behavior.
UpdatePreferences	SubsystemPreferences for platform update behavior.
UserSubsystemPreferences	Full preferences stored for a user.
VideoPreferences	SubsystemPreferences for map control behavior.

Enum Summary

LayoutPosition	A LayoutPosition specifies where (in a typical border-type layout) a component should go.
MapsetStartupVisibility	The three possible states for mapset visibility at startup.
RenderEngine	The RenderEngine is the main driver used for map rendering.
RenderingHint	RenderingHint are suggestions made to the underlying rendering engine on how to choose between alternate methods and algorithms for specific tasks like anti-aliasing.
RenderQuality	RenderQuality is a general indicator of settings used for rendering.
Subsystem	This is an enumeration of standard subsystems managed by preferences.
TextureFiltering	TextureFiltering is a technique used to scale textures outside of their native resolution (larger or smaller).

Package com.partnersoft.preferences.model Description

End-user preferences data models.

These classes represent the preferences models for various subsystems.

While not ideal, these are stored here rather than with the subsystems they correspond to, mostly to keep them in one place. This decision may change in the future.

Copyright 2009 Partner Software, Inc.

Version:

$Id$

Author:

Paul Reavis