modules/controls/src/main/java/javafx/scene/control/DialogPane.java

Print this page
rev 9240 : 8076423: JEP 253: Prepare JavaFX UI Controls & CSS APIs for Modularization


  48 import javafx.css.CssMetaData;
  49 import javafx.css.StyleOrigin;
  50 import javafx.css.Styleable;
  51 import javafx.css.StyleableObjectProperty;
  52 import javafx.css.StyleableProperty;
  53 import javafx.css.StyleableStringProperty;
  54 import javafx.event.ActionEvent;
  55 import javafx.geometry.Pos;
  56 import javafx.scene.Node;
  57 import javafx.scene.control.ButtonBar.ButtonData;
  58 import javafx.scene.image.Image;
  59 import javafx.scene.image.ImageView;
  60 import javafx.scene.layout.ColumnConstraints;
  61 import javafx.scene.layout.GridPane;
  62 import javafx.scene.layout.Pane;
  63 import javafx.scene.layout.Priority;
  64 import javafx.scene.layout.Region;
  65 import javafx.scene.layout.StackPane;
  66 
  67 import com.sun.javafx.css.StyleManager;
  68 import com.sun.javafx.css.converters.StringConverter;
  69 
  70 /**
  71  * DialogPane should be considered to be the root node displayed within a
  72  * {@link Dialog} instance. In this role, the DialogPane is responsible for the
  73  * placement of {@link #headerProperty() headers}, {@link #graphicProperty() graphics},
  74  * {@link #contentProperty() content}, and {@link #getButtonTypes() buttons}.
  75  * The default implementation of DialogPane (that is, the DialogPane class itself)
  76  * handles the layout via the normal {@link #layoutChildren()} method. This 
  77  * method may be overridden by subclasses wishing to handle the layout in an 
  78  * alternative fashion).
  79  * 
  80  * <p>In addition to the {@link #headerProperty() header} and 
  81  * {@link #contentProperty() content} properties, there exists 
  82  * {@link #headerTextProperty() header text} and 
  83  * {@link #contentTextProperty() content text} properties. The way the *Text
  84  * properties work is that they are a lower precedence compared to the Node
  85  * properties, but they are far more convenient for developers in the common case,
  86  * as it is likely the case that a developer more often than not simply wants to
  87  * set a string value into the header or content areas of the DialogPane.
  88  *




  48 import javafx.css.CssMetaData;
  49 import javafx.css.StyleOrigin;
  50 import javafx.css.Styleable;
  51 import javafx.css.StyleableObjectProperty;
  52 import javafx.css.StyleableProperty;
  53 import javafx.css.StyleableStringProperty;
  54 import javafx.event.ActionEvent;
  55 import javafx.geometry.Pos;
  56 import javafx.scene.Node;
  57 import javafx.scene.control.ButtonBar.ButtonData;
  58 import javafx.scene.image.Image;
  59 import javafx.scene.image.ImageView;
  60 import javafx.scene.layout.ColumnConstraints;
  61 import javafx.scene.layout.GridPane;
  62 import javafx.scene.layout.Pane;
  63 import javafx.scene.layout.Priority;
  64 import javafx.scene.layout.Region;
  65 import javafx.scene.layout.StackPane;
  66 
  67 import com.sun.javafx.css.StyleManager;
  68 import javafx.css.converter.StringConverter;
  69 
  70 /**
  71  * DialogPane should be considered to be the root node displayed within a
  72  * {@link Dialog} instance. In this role, the DialogPane is responsible for the
  73  * placement of {@link #headerProperty() headers}, {@link #graphicProperty() graphics},
  74  * {@link #contentProperty() content}, and {@link #getButtonTypes() buttons}.
  75  * The default implementation of DialogPane (that is, the DialogPane class itself)
  76  * handles the layout via the normal {@link #layoutChildren()} method. This 
  77  * method may be overridden by subclasses wishing to handle the layout in an 
  78  * alternative fashion).
  79  * 
  80  * <p>In addition to the {@link #headerProperty() header} and 
  81  * {@link #contentProperty() content} properties, there exists 
  82  * {@link #headerTextProperty() header text} and 
  83  * {@link #contentTextProperty() content text} properties. The way the *Text
  84  * properties work is that they are a lower precedence compared to the Node
  85  * properties, but they are far more convenient for developers in the common case,
  86  * as it is likely the case that a developer more often than not simply wants to
  87  * set a string value into the header or content areas of the DialogPane.
  88  *