151 * <p>
152 * The set of defaults a particular look and feel supports is defined
153 * and documented by that look and feel. In addition, each look and
154 * feel, or {@code ComponentUI} provided by a look and feel, may
155 * access the defaults at different times in their life cycle. Some
156 * look and feels may aggressively look up defaults, so that changing a
157 * default may not have an effect after installing the look and feel.
158 * Other look and feels may lazily access defaults so that a change to
159 * the defaults may effect an existing look and feel. Finally, other look
160 * and feels might not configure themselves from the defaults table in
161 * any way. None-the-less it is usually the case that a look and feel
162 * expects certain defaults, so that in general
163 * a {@code ComponentUI} provided by one look and feel will not
164 * work with another look and feel.
165 * <p>
166 * <strong>Warning:</strong>
167 * Serialized objects of this class will not be compatible with
168 * future Swing releases. The current serialization support is
169 * appropriate for short term storage or RMI between applications running
170 * the same version of Swing. As of 1.4, support for long term storage
171 * of all JavaBeans™
172 * has been added to the <code>java.beans</code> package.
173 * Please see {@link java.beans.XMLEncoder}.
174 *
175 * @author Thomas Ball
176 * @author Hans Muller
177 * @since 1.2
178 */
179 @SuppressWarnings("serial") // Same-version serialization only
180 public class UIManager implements Serializable
181 {
182 /**
183 * This class defines the state managed by the <code>UIManager</code>. For
184 * Swing applications the fields in this class could just as well
185 * be static members of <code>UIManager</code> however we give them
186 * "AppContext"
187 * scope instead so that applets (and potentially multiple lightweight
188 * applications running in a single VM) have their own state. For example,
189 * an applet can alter its look and feel, see <code>setLookAndFeel</code>.
190 * Doing so has no affect on other applets (or the browser).
191 */
|
151 * <p>
152 * The set of defaults a particular look and feel supports is defined
153 * and documented by that look and feel. In addition, each look and
154 * feel, or {@code ComponentUI} provided by a look and feel, may
155 * access the defaults at different times in their life cycle. Some
156 * look and feels may aggressively look up defaults, so that changing a
157 * default may not have an effect after installing the look and feel.
158 * Other look and feels may lazily access defaults so that a change to
159 * the defaults may effect an existing look and feel. Finally, other look
160 * and feels might not configure themselves from the defaults table in
161 * any way. None-the-less it is usually the case that a look and feel
162 * expects certain defaults, so that in general
163 * a {@code ComponentUI} provided by one look and feel will not
164 * work with another look and feel.
165 * <p>
166 * <strong>Warning:</strong>
167 * Serialized objects of this class will not be compatible with
168 * future Swing releases. The current serialization support is
169 * appropriate for short term storage or RMI between applications running
170 * the same version of Swing. As of 1.4, support for long term storage
171 * of all JavaBeans
172 * has been added to the <code>java.beans</code> package.
173 * Please see {@link java.beans.XMLEncoder}.
174 *
175 * @author Thomas Ball
176 * @author Hans Muller
177 * @since 1.2
178 */
179 @SuppressWarnings("serial") // Same-version serialization only
180 public class UIManager implements Serializable
181 {
182 /**
183 * This class defines the state managed by the <code>UIManager</code>. For
184 * Swing applications the fields in this class could just as well
185 * be static members of <code>UIManager</code> however we give them
186 * "AppContext"
187 * scope instead so that applets (and potentially multiple lightweight
188 * applications running in a single VM) have their own state. For example,
189 * an applet can alter its look and feel, see <code>setLookAndFeel</code>.
190 * Doing so has no affect on other applets (or the browser).
191 */
|