![[An illustration showing raised and lowered BevelBorders]](../border/doc-files/BevelBorder-1.png)
+ * alt="[An illustration showing raised and lowered BevelBorders]" />
![[An illustration showing BevelBorders that were
- * constructed with this method]](../border/doc-files/BevelBorder-2.png)
+ * constructed with this method]" />
![[An illustration showing BevelBorders that
- * were constructed with this method]](../border/doc-files/BevelBorder-3.png)
+ * were constructed with this method]" />
![[An illustration of EmptyBorder]](../border/doc-files/EmptyBorder-1.png)
+ * alt="[An illustration of EmptyBorder]" />
![[An illustration of the two EtchedBorder
- * variants]](../border/doc-files/EtchedBorder-1.png)
+ * variants]" />
+ * EtchedBorder variants]" />
![[An illustration that shows which pixels get
- * painted in what color]](../border/doc-files/EtchedBorder-2.png)
+ * painted in what color]" />
![[An illustration of two LineBorders] />
+ * height=](../border/doc-files/LineBorder-1.png)
![[An illustration of two MatteBorders] />
+ * height=](../border/doc-files/MatteBorder-1.png)
![[A picture of a MatteBorder made by this
- * constructor]](../border/doc-files/MatteBorder-2.png)
+ * constructor]" />
![[A picture of a MatteBorder made by this
- * constructor]](../border/doc-files/MatteBorder-4.png)
+ * constructor]" />
![[A picture of a MatteBorder made by this
- * constructor]](../border/doc-files/MatteBorder-6.png)
+ * constructor]" />
![[UML diagram illustrating the architecture for pluggable
- * look and feels]](doc-files/ComponentUI-1.png)
+ * look and feels]" />
Components such as address@hidden javax.swing.JSlider} do not directly
* implement operations related to the look and feel of the user
@@ -68,14 +68,14 @@
* services. Soon before the end of its lifecycle, the
* ComponentUI will receive an address@hidden #uninstallUI}
* message, at which time the ComponentUI is expected to
- * undo any changes.
+ * undo any changes.
Note that the ui of a JComponent
* changes whenever the user switches between look and feels. For
* example, the ui property of a JSlider
* could change from an instance of MetalSliderUI to an
* instance of FooSliderUI. This switch can happen at any
- * time, but it will always be performed from inside the Swing thread.
+ * time, but it will always be performed from inside the Swing thread.
installUI
* message.
*
- * This method should perform the following tasks: - * - *
- Set visual properties such as borders, fonts, colors, or - * icons. However, no change should be performed for those - * properties whose values have been directly set by the client - * application. To allow the distinction, LookAndFeels are expected - * to use values that implement the address@hidden UIResource} marker - * interface, such as address@hidden BorderUIResource} or address@hidden - * ColorUIResource}. + *
- Set visual properties such as borders, fonts, colors, or + * icons. However, no change should be performed for those + * properties whose values have been directly set by the client + * application. To allow the distinction, LookAndFeels are expected + * to use values that implement the address@hidden UIResource} marker + * interface, such as address@hidden BorderUIResource} or address@hidden + * ColorUIResource}. *
- If necessary, install a address@hidden java.awt.LayoutManager}. - * *
- Embed custom sub-components. For instance, the UI delegate - * for a address@hidden javax.swing.JSplitPane} might install a special - * component for the divider. - * + * for a address@hidden javax.swing.JSplitPane} might install a special + * component for the divider. *
- Register event listeners. - * *
- Set up properties related to keyborad navigation, such as - * mnemonics or focus traversal policies.
This method should perform the following tasks:
* + *-
+ *
UndoableEdits.
*
* The use of a CompoundEdit is divided in two separate
- * phases.
- *
- *
- In the first phase, the
CompoundEditis - * initialized. After a new instance ofCompoundEdithas - * been created, address@hidden #addEdit(UndoableEdit)} is called for each - * element of the compound. To terminate the initialization phase, - * call address@hidden #end()}.
+ * phases.
*
+ * - In the first phase, the
CompoundEditis + * initialized. After a new instance ofCompoundEdithas + * been created, address@hidden #addEdit(UndoableEdit)} is called for each + * element of the compound. To terminate the initialization phase, + * call address@hidden #end()}.
* - In the second phase, the the
CompoundEditcan be - * used, typically by invoking address@hidden #undo()} and address@hidden - * #redo()}.
-
+ *
The following example shows how to use this class. + *
The following example shows how to use this class.
* - * Foo foo; // class Foo implements address@hidden StateEditable}
- * StateEdit edit;
- *
- * edit = new StateEdit(foo, "Name Change");
- * foo.setName("Jane Doe");
- * edit.end();
- * undoManager.addEdit(edit);
+ *
+ * Foo foo; // class Foo implements address@hidden StateEditable}
+ * StateEdit edit;
+ *
+ * edit = new StateEdit(foo, "Name Change");
+ * foo.setName("Jane Doe");
+ * edit.end();
+ * undoManager.addEdit(edit);
+ *
*
* If Foo’s implementation of address@hidden
* StateEditable} considers the name as part of the editable state,
* the user can now choose “Undo Name Change” or
* “Redo Name Change” from the respective menu. No
- * further undo support is needed from the application.
- *
- *
The following explains what happens in the example. + * further undo support is needed from the application.
* - *- When a
StateEditis created, the associated - * address@hidden StateEditable} gets asked to store its state into a hash - * table, address@hidden #preState}.
+ * - When a
StateEditis created, the associated + * address@hidden StateEditable} gets asked to store its state into a hash + * table, address@hidden #preState}.
* - The application will now perform some changes to the edited - * object. This typically happens by invoking methods on the edited - * object. - * + * object. This typically happens by invoking methods on the edited + * object. *
- The editing phase is terminated by invoking the address@hidden #end()}
- * method of the
StateEdit. Theend()method - * does two things. - * - *- The edited object receives a second request for storing - * its state. This time, it will use a different hash table, address@hidden - * #postState}. - * - *
- To increase efficiency, the
StateEditnow removes - * any entries from address@hidden #preState} and address@hidden #postState} that have - * the same key, and whose values are equal. Equality is determined - * by invoking theequalsmethod inherited from - * address@hidden java.lang.Object}.
+ * method of the - The edited object receives a second request for storing + * its state. This time, it will use a different hash table, address@hidden + * #postState}. + *
- To increase efficiency, the
StateEditnow removes + * any entries from address@hidden #preState} and address@hidden #postState} that have + * the same key, and whose values are equal. Equality is determined + * by invoking theequalsmethod inherited from + * address@hidden java.lang.Object}.
+ * - When the user later chooses to undo the
StateEdit, * the edited object is asked to address@hidden StateEditable#restoreState * restore its state} from the address@hidden #preState} table. Similarly, * when the user chooses to redo theStateEdit, * the edited object gets asked to restore its state from the address@hidden - * #postState}.
The following explains what happens in the example.
* + *-
+ *
StateEdit. The end() method
+ * does two things.
*
+ * -
+ *