The tool provides two ways to quickly create new Data
- Bindings: the Data Bindings menu and the bindings property in
- the property pane.
-
-
-
-
Data Binding Menu
-
The Data Bindings menu provides the ability to
- quickly create a data binding for a widget. If the widget does not
- have any data bindings, the menu immediately cascades out to show the
- available properties of the widget that can be bound to a model property. If
- the widget has existing data bindings, those are shown at the top of the
- cascaded menu and a list of widget properties is shown in a submenu.
- Clicking on an unbound property will open the Create Data
- Binding wizard.
-
-
-
Bindings Property
-
The bindings property in the property
- pane opens up to show a list of all bindable properties of the
- widget. Clicking the
-
- button next to an unbound property will open the Create Data
- Binding wizard.
-
-
-
-
-
-
-
-
-
- Choose Model
-
- The first page of the Create Data Binding wizard is used to select
- the model and property to bind the selected target property to. Two types
- of targets and models are supported:
-
- Beans and
-
- Widgets. The filter field above the list can be used to filter the
- list of items. The
-
- clear button can be used to clear the filter and restore the full list.
-
-
-
-
-
-
-
-
-
-
- Beans: any field of the current compilation unit may be selected.
-
-
-
-
-
-
-
-
-
-
- Widgets: any widget in the current compilation unit may be selected.
-
-
-
-
-
-
-
-
When any Model object is selected,
-
-
its properties (bean fields or standard Swing widget
- properties) are shown in the associated Properties list. Properties may be expanded to show
- their nested attributes. A drop down filter menu is
- available to filter the Property list by type and hide or show the advanced
- properties. Supported filters are
- String, Boolean, Numbers, Color, Font and
- Image.
-
-
-
-
-
-
-
Once the model property has been selected, click the Finish
- button to create a new data binding using default options. If you wish
- to customize the properties of the data binding, click the Next
- button to go to the second page of the wizard.
-
- Properties
-
- The second page of the Create Data Binding wizard is used to
- customize the properties of the data binding itself. When creating a
- binding, the update strategy from
- target to model and model to target may be specified as well as
- any strategy-specific properties (validators and converters).
-
-
-
-
-
-
-
-
When the Target or Model is a Text widget and the text
- property is selected, the triggering event may be specified as Swing.Modify,
- Swing.FocusOut or Swing.NONE.
-
-
-
Predefined update value strategies - READ_ONCE,
- READ and READ_WRITE - may be selected.
-
-
-
-
-
-
- Source
-
Clicking the Finish button will generate
- the necessary data binding code which may then be seen in the Source
- view. An initDataBindings() method is created, if it does not
- already exist and a call to that method is added to the end of the
- widget creation process. Within the initDataBindings()
- method, any needed bean properties are created followed by the
- creation of each binding.
-
-
-
Warning: do not edit the
- initDataBinding() method by hand (without carefully matching the
- code generation pattern used by the tool) as it will be regenerated
- in its entirety any time the tool needs to add, remove or update a
- data binding.
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/features/swing/data_binding/edit_data_binding_dialog.html b/org.eclipse.wb.swing.doc.user/html/features/swing/data_binding/edit_data_binding_dialog.html
deleted file mode 100644
index 008af96cf..000000000
--- a/org.eclipse.wb.swing.doc.user/html/features/swing/data_binding/edit_data_binding_dialog.html
+++ /dev/null
@@ -1,104 +0,0 @@
-
-
-Edit Data Binding Dialog
-
-
-
-
-
Edit Data Binding Dialog
-
Supported for JDK 1.5
- and above only
-
The tool provides two ways to quickly edit existing Data
- Bindings: the Data Bindings menu and the bindings property in
- the property pane.
-
-
-
-
-
-
Data Binding Menu
-
The Data Bindings menu provides the ability to quickly
- edit a data binding for a widget. If the widget has existing data
- bindings, those are shown at the top of the cascaded menu and a list
- of widget properties is shown in a submenu. Clicking on a bound
- property will open the
- Edit Data Binding dialog.
-
-
-
Bindings Property
-
The bindings property in the property pane
- opens up to show a list of all bindable properties of the widget.
- Clicking the
-
- button next to a bound property will open the Edit Data
- Binding dialog.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
The Edit Data
- Binding dialog is used to
- customize the properties of the data binding itself. When editing a
- binding, the update strategy from
- target to model and model to target may be specified as well as
- any strategy-specific properties (validators and converters).
-
When the Target or Model is a Text widget and the text
- property is selected, the triggering event may be specified as Swing.Modify,
- Swing.FocusOut or Swing.NONE.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Predefined update value strategies - READ_ONCE,
- READ and READ_WRITE - may be selected.
-
-
-
-
-
-
When binding to a <EL Expression>, a text field is
- provided where the expression may be entered.
-
-
-
- Source
-
Clicking the Finish button will generate
- the necessary data binding code which may then be seen in the Source
- view. An initDataBindings() method is created, if it does not
- already exist and a call the that method is added to the end of the
- widget creation process. Within the initDataBindings()
- method, any needed bean properties are created followed by the
- creation of each binding.
-
-
-
Warning: do not edit the
- initDataBinding() method by hand (without carefully matching the
- code generation pattern used by the tool) as it will be regenerated
- in its entirety any time the tool needs to add, remove or update a
- data binding.
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/features/swing/data_binding/example.html b/org.eclipse.wb.swing.doc.user/html/features/swing/data_binding/example.html
deleted file mode 100644
index 8dac6c9ad..000000000
--- a/org.eclipse.wb.swing.doc.user/html/features/swing/data_binding/example.html
+++ /dev/null
@@ -1,168 +0,0 @@
-
-
-Swing Data Binding Example
-
-
-
-
-
Swing Data Binding Example
-
Supported for JDK 1.5
- and above only
-
-
-
As an example of how the the data binding tools can be
- used, consider the following Phone Book example. The phone book
- manages a set of phone groups. Each phone group in turn holds onto one or
- more persons. For each person, various e-mail and phone contact information
- is maintained. Editing a person's description should update the same data
- shown in the list. The final code for the Phone Book project is available
- here.
-
-
-
-
-
Use Designer to create the skeleton of the
- JPhoneBook.java class
-
-
-
-
-
Create the following model classes:
-
-
-
-
-
Class Person with properties: name,
- email, phone, mobilePhone1, mobilePhone2
-
-
Class PhoneGroup with properties: name,
- persons
-
-
Class PhoneGroups with properties:
- groups
-
-
-
-
-
Add the following to the JPhoneBook class:
-
- private PhoneGroups
- m_groups = new PhoneGroups();
-
- And add some initial data:
-
- PhoneGroup group1 = new
- PhoneGroup("Developer Team");
- m_groups.addGroup(group1);
- group1.addPerson(new Person("Konstantin Scheglov",
- "kosta@nospam.com", "1234567890", "", ""));
- group1.addPerson(new Person("Alexander Mitin",
- "mitin@nospam.com", "", "0987654321", ""));
- group1.addPerson(new Person("Alexander Lobas",
- "lobas@nospam.com", "", "", "111-222-333-00"));
-
-
-
Set the content for the group viewer. Click the
- Bindings tab in the editor. Select m_groupList in the
- Targets (Widgets)
- list, <Self Object> in the Target Properties list, select m_groups in the
-
- Model (Beans) list, and groups in the Model Properties list.
-
-
-
-
-
Click the
-
- Bind button to open the Create Data Binding dialog. m_groups.group
- contains elements of type PhoneGroup, so select the type
- PhoneGroup and its <EL Expression> property. In the EL
- Expression field, type "${name} ({$personCount})". Note that selecting
- the name property would result in just the name of the group
- being displayed. You can use EL Expressions to create more complex
- results. In this case, we can show the name plus the number of people in
- the group.
-
-
-
-
-
Click OK to see m_groups.groups bound to
- m_groupsList in the table. You can also see that the detail
- binding between m_groupsList and the EL Expression has
- also been created.
-
-
-
-
-
Run the application to see that the list of phone
- groups is populated and that each group shows its person count.
-
-
-
-
-
Next we would like selecting a group to show all of
- its contained persons. Switch back to the
- Bindings tab.
- Select the <Self Object> of the m_personTable in the Target
- Widget list and
- m_groupList and selectedElement/persons in the Model Widget list and click the
-
- Bind button to open the Create Data Binding dialog.
-
-
-
-
-
-
We need to show the properties of a Person object in
- m_personTable, so click the Add button to add a table column
- binding for each property (name, email, phone,
- mobilePhone1 and mobilePhone2). You can order the Person
- properties using the << and >> buttons
-
-
-
-
-
Click OK twice and run the application. See
- that selecting a group now updates the Persons list.
-
-
-
-
-
Switch back to the
- Bindings tab. Next we need to bind selectedElement of the m_personTable (a
- Person object) into the various text editors.
-
-
-
-
-
Select the first Text widget (m_nameTextField)
- and its text property and the m_personTable and its
- selectedElement/name property. Click the
-
- Bind button to open the Create Data Binding dialog. Leave
- everything set to the defaults and click the OK button.
-
-
-
-
-
Bind each selectedElement property to its associated
- Text field.
-
-
-
-
-
Run the application. See that selecting a
- group updates the Persons list and selecting a Person now
- updates each of the Text fields.
-
-
-
-
-
Also note that changing any of the data in the text
- fields immediately updates the data in the table. The magic of data
- binding!
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/features/swing/data_binding/index.html b/org.eclipse.wb.swing.doc.user/html/features/swing/data_binding/index.html
deleted file mode 100644
index ef9867c52..000000000
--- a/org.eclipse.wb.swing.doc.user/html/features/swing/data_binding/index.html
+++ /dev/null
@@ -1,109 +0,0 @@
-
-
-Swing Data Binding
-
-
-
-
-
Swing Data Binding
-
-
Note: In order to use Swing Data
- Binding (JSR 295), you must first add the Swing Data Binding jar (e.g.,
- beansbinding-1.2.1.jar) to your classpath.
-
The tool can create new Data Bindings in several
- different ways:
-
-
-
Click the
- Bindings tab in the editor to created and edit
- the bindings.
-
-
Right-clicking on a widget and selecting the
- Data Binding menu.
-
-
Expanding the bindings property in the
- property pane.
-
-
Use the
- Swing Automatic Data Binding
- wizard to create a complete user interface from a domain (bean)
- class.
-
-
The tool will generate or update any necessary data binding
- code which may then be seen in the Source
- view.
The Data Bindings menu provides the ability to
- quickly create or edit data bindings for a widget. If the widget does not
- have any data bindings, the menu immediately cascades out to show the
- available properties of the widget that can be bound to a model property. If
- the widget has existing data bindings, those are shown at the top of the
- cascaded menu followed by a separator and a list of widget properties.
- Clicking on an unbound property will open the
- Create Data
- Binding wizard while clicking a bound property will open
- the Edit Data Binding
- dialog.
-
- .
-
Bindings
- Property
-
The bindings property in the property
- pane opens up to show a list of all bindable properties of the
- widget. Clicking the
-
- button next to an unbound property will open the
- Create Data
- Binding wizard while clicking the
-
- button next to a bound property will open the
- Edit Data Binding dialog.
-
- .
-
Automatic Data Binding Wizard
-
The
- Swing Automatic Data Binding wizard can be used
- to create new user interface classes (Composites, Dialogs or Windows)
- complete with widgets, layouts and data bindings from arbitrary domain model
- (bean) classes..
-
-
-
-
Icon
- Decorator
-
Any widget with a data binding assigned to will show up in
- the component tree with an icon decorator:
-
-
-
-
-
- Source
-
The tool will generate or update any necessary data binding
- code which may then be seen in the Source view. An initDataBindings()
- method is created, if it does not already exist and a call to that
- method is added to the end of the widget creation process.
-
Within the initDataBindings() method, any needed
- bean properties are created followed by the creation of each binding.
-
-
-
Warning: do not edit the initDataBinding()
- method by hand (without carefully matching the code generation pattern used
- by the tool) as it will be regenerated in its entirety any time
- the tool needs to add, remove or update a data binding.
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/features/swing/data_binding/swing_bindings.html b/org.eclipse.wb.swing.doc.user/html/features/swing/data_binding/swing_bindings.html
deleted file mode 100644
index 72921cea4..000000000
--- a/org.eclipse.wb.swing.doc.user/html/features/swing/data_binding/swing_bindings.html
+++ /dev/null
@@ -1,144 +0,0 @@
-
-
-Swing Data Bindings
-
-
-
-
-
Swing Data Bindings
-
Supported for JDK 1.5
- and above only
-
Click the
- Bindings tab in the editor to created and edit
- data bindings.
-
-
-
-
-
Swing uses simple bindings between targets and models.
-
Target & Model Types
-
Two types of targets and models are supported:
-
-
-
-
- Beans: any field of the current compilation unit may be selected.
- The filter field above the list can be used to filter the list of beans.
- The
-
- clear button can be used to clear the filter and restore the full list.
- Beans are the primary data source for bindings (usually the
- model). Any property of the Bean may be observed. Individual
- beans may also be expanded to reveal their direct sub properties.
-
-
-
-
-
-
-
- Widgets: any widget in the current compilation unit may be selected.
- If a widget is not a field, it will be converted to a field
- automatically. The filter field above the list can be used to filter the
- list of widgets. The
-
- clear button can be used to clear the filter and restore the full list.
- Any property of the Widget may be observed.
-
-
-
-
-
Properties
-
When any Target or Model object is selected,
- its properties (bean fields or standard Swing widget properties) are shown
- in the associated Properties list. Properties may be expanded to show
- their nested attributes. A drop down filter menu is
- available to filter the Property list by type and hide or show the advanced
- properties. Supported filters are
- String, Boolean, Numbers, Color, Font and
- Image.
-
-
-
-
-
-
-
New Swing Bindings
-
New bindings are created by selecting a Target, a
- Target Property, a Source, a Source Property and
- clicking the
-
- Bind button. When creating a binding, the update strategy from
- target to model and model to target may be specified as well as
- any strategy-specific properties (converter and validator).
-
-
-
When the Target or Model is a Text widget and the text
- property is selected, the triggering event may be specified as Swing.Modify,
- Swing.FocusOut or Swing.NONE.
-
-
-
Predefined update value strategies - READ_ONCE,
- READ and READ_WRITE - may be selected.
-
-
-
When binding to a <EL Expression>, a text field is
- provided where the expression may be entered.
-
-
-
- When binding a JList to a collection of model objects, the detail of the
- model (what is shown in the list) can be specified.
-
-
-
- When binding a JTable to a collection of model objects, column bindings may
- be added for each model object property.
-
-
-
Existing Swing Bindings
-
At the top of the page, existing Bound Properties
- are listed. The Target and Model are shown as well as the
- Strategy and the Binding variable name.
-
-
-
Clicking the
-
- Edit button or Edit menu opens the Edit Binding dialog
- where the update strategy, converter and validator may be modified.
-
-
-
The
-
- Delete button or Delete menu is used to delete the selected
- bound property while the
-
- Delete All button or Delete All menu is used to delete all of
- the bound properties.
-
The
-
- Move Up and
-
- Move Down buttons and menus are used to change the order of the
- bindings while the
-
- Goto Definition button and menu are used to jump to the generated
- code for the binding.
-
- Source
-
As bindings are created or edited on the Bindings tab,
- the necessary data binding
- code is generated which may then be seen in the Source view. An initDataBindings()
- method is created, if it does not already exist and a call to that
- method is added to the end of the widget creation process.
-
Within the initDataBindings() method, any needed
- bean properties are created followed by the creation of each binding.
-
-
-
Warning: do not edit the initDataBinding()
- method by hand (without carefully matching the code generation pattern used
- by the tool) as it will be regenerated in its entirety any time
- the tool
- needs to add, remove or update a data binding.
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/features/swing_code_generation.html b/org.eclipse.wb.swing.doc.user/html/features/swing_code_generation.html
deleted file mode 100644
index 676330069..000000000
--- a/org.eclipse.wb.swing.doc.user/html/features/swing_code_generation.html
+++ /dev/null
@@ -1,185 +0,0 @@
-
-Preferences - Swing > Code Generation
-
-
-
-
Swing Code Generation
-
-
-
Swing Designer supports a wide variety of code generation styles
- and can emulate most other Java GUI builders including NetBeans,
- JBuilder, the Eclipse Visual Editor, etc. Choose a
- Variable
- Generation style (Local,
- Field, Initialized Field or
- Lazy) and a Statement Generation style (Flat or
- Block). Many of the styles have additional options that can be set.
- Once any combination of settings is selected, you can see a preview of
- that code generation style in the Preview pane.
-
- You can also specify in which method components will be created by default
- (in the event that a suitable method has not already be
- defined for the current class). If the method does not exist, it will be
- created and a call to it added to the constructor for the class. Various
- default choices are provided to match the code generation patterns of
- other GUI builders.
- In the Local variable generation style, each component is
- assigned to a unique local variable and initialized at the point of
- declaration. An option is provided to declare each variable as final.
- Note that component types marked as As Field on the
- Variables > Type
- Specific preference page will always be assigned to fields.
- In the Field generation style, each component is
- assigned to a unique field and initialized at the point where it is
- first used. An option is provided to prefix each field reference with
- this.
- In the Initialized Field generation style, each component is
- assigned to a unique field and initialized at the point at the point of
- declaration. An option is provided to prefix each field reference with
- this.
- In the Lazy generation style, each component is created in its
- own unique getXXX() method. An option is provided to set the
- visibility modifier to private, package private,
- protected or public.
In flat mode, each component is created in the same scope at
- the same indentation level. An option is provided to prefix the creation
- of each component with either a blank line or a comment.
In block mode, each component is created in its own scoped
- code block. Child components are created in nested blocks.
-
-
-
Local
- Variables / Flat Mode
-
-
-
Local
- Variables / Block Mode
-
-
-
-
-
Fields / Flat Mode
-
-
-
Fields / Block Mode
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/absolutelayout.html b/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/absolutelayout.html
deleted file mode 100644
index e610fd936..000000000
--- a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/absolutelayout.html
+++ /dev/null
@@ -1,129 +0,0 @@
-
-
-
-
- Swing Absolute Layout
-
-
-
-
-
Swing Absolute Layout
-
-
-
Absolute Layout or Null Layout is a simple x,y
- oriented layout. During layout, the live component is shown moving with a tooltip showing its
-current location or size. Dynamic snap / alignment points are provided to make it
-convenient to align the component with other components or the window margin.
- Resizing a component also snaps to the preferred size of the resized
- component or to the size (vertical or horizontal) of any other component
- on the same parent.
Select Absolute Layout from the Layouts palette and
- drop it on a JFrame or JPanel
-
-
-
-
-
-
-
Graphical feedback is provided for all widget size and
- position operations
-
-
-
-
-
-
-
-
Graphical Feedback
-
-
Position and size widgets using snapping feedback
-
-
-
-
-
-
-
-
Provide position and size feedback via tooltips
-
-
-
-
-
-
-
-
Align widgets horizontally and vertically
-
-
-
-
-
-
-
-
Indent widgets intelligently
-
-
-
-
-
-
-
Align widgets along text baselines
-
-
-
-
-
-
-
-
Align widgets to margins
-
-
-
-
-
-
-
Replicate widget heights and widths
-
-
-
-
-
-
-
-
Align widgets using optional grid
-
-
-
-
-
-
-
Align and center widgets using toolbar
-
-
-
-
-
-
-
Set alignment and size using floating layout assistant
-
Set size, location and/or bounds properties using
- the
-
- Property Pane
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/borderlayout.html b/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/borderlayout.html
deleted file mode 100644
index 732046af8..000000000
--- a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/borderlayout.html
+++ /dev/null
@@ -1,75 +0,0 @@
-
-
-
-
- Swing BorderLayout
-
-
-
-
-
Swing BorderLayout
-
-
-
BorderLayout lays out a container, arranging and resizing its
- components to fit in five regions: north, south, east,
- west, and center. Each region may contain no more than one
- component, and is identified by a corresponding constant: NORTH,
- SOUTH, EAST, WEST, and CENTER. When adding a
- component to a container with a border layout, use one of these five
- constants. As a convenience, BorderLayout interprets the absence
- of a string specification the same as the constant CENTER.
Select BorderLayout from the Layouts palette and
- drop it on a JFrame or JPanel
-
-
-
-
-
-
-
Graphical feedback is provided for all drop and move
- interactions
-
-
-
-
-
-
-
Horizontal and vertical gaps can be specified using the
- Property Pane
-
-
-
-
-
-
-
Constraints can be specified using the
- Property Pane
-
-
-
-
-
-
-
Graphical Feedback
-
-
When moving a widget or adding a new widget, open cells are
- highlighted green while the current drop point is highlighted in yellow
-
-
-
-
-
Attempting to drop into an already occupied cell is blocked
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/boxlayout.html b/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/boxlayout.html
deleted file mode 100644
index 452ab68d3..000000000
--- a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/boxlayout.html
+++ /dev/null
@@ -1,151 +0,0 @@
-
-
-
-
- Swing BoxLayout
-
-
-
-
-
Swing BoxLayout
-
-
-
BoxLayout allows multiple components to be laid out either
- vertically or horizontally. The components will not wrap so, for
- example, a vertical arrangement of components will stay vertically
- arranged when the frame is resized. Nesting multiple panels with
- different combinations of horizontal and vertical gives an effect
- similar to GridBagLayout, without the complexity. The
- BoxLayout manager is constructed with an axis parameter that
- specifies the type of layout that will be done. For all directions,
- components are arranged in the same order as they were added to the
- container.
-
- BoxLayout attempts to arrange components at their preferred
- widths (for horizontal layout) or heights (for vertical layout). For a
- horizontal layout, if not all the components are the same height,
- BoxLayout attempts to make all the components as high as the highest
- component. If that's not possible for a particular component, then
- BoxLayout aligns that component vertically, according to the
- component's Y alignment. By default, a component has a Y alignment of
- 0.5, which means that the vertical center of the component should have
- the same Y coordinate as the vertical centers of other components with
- 0.5 Y alignment. Similarly, for a vertical layout, BoxLayout
- attempts to make all components in the column as wide as the widest
- component. If that fails, it aligns them horizontally according to their
- X alignments.
Graphically show area occupied by struts and springs (glue)
-
-
-
-
-
-
-
Graphically resize struts and rigid areas via dragging
-
-
-
-
-
-
-
-
Direct-edit (hit space bar) struts and rigid areas to resize
- them
-
-
-
-
-
-
-
-
Resize struts and rigid areas using the
- Property Pane
-
-
-
-
-
-
-
-
Orientation can be specified using the
- Property Pane
-
-
-
-
-
-
-
Widget alignment within the BoxLayout can be set using
- the
- Property Pane
-
-
-
-
-
-
Note that struts and rigid areas can be used as invisible spacer
- objects in other layouts as well
-
-
-
-
-
-
-
-
-
-
-
Graphical Feedback
-
-
When moving a widget or adding a new widget, the current drop
- point is highlighted in red
-
-
-
-
-
-
-
Resize struts and rigid areas by dragging or direct edit
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/cardlayout.html b/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/cardlayout.html
deleted file mode 100644
index 101b08def..000000000
--- a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/cardlayout.html
+++ /dev/null
@@ -1,62 +0,0 @@
-
-
-
-
- Swing GridLayout
-
-
-
-
-
Swing CardLayout
-
-
-
A CardLayout object is a layout manager for a container. It
- treats each component in the container as a card. Only one card is
- visible at a time, and the container acts as a stack of cards. The first
- component added to a CardLayout object is the visible component
- when the container is first displayed. The ordering of cards is
- determined by the container's own internal ordering of its component
- objects. CardLayout defines a set of methods that allow an
- application to flip through these cards sequentially, or to show a
- specified card.
-
Main Features
-
-
Select CardLayout from the Layouts palette and
- drop it on a JFrame or JPanel
-
-
-
-
-
-
-
When adding a new widget, the current drop point is
- highlighted in green
-
-
-
-
-
-
-
-
Switch between cards using the up/down arrows in the upper
- right corner
-
-
-
-
-
-
-
-
Horizontal and vertical margins can be specified using the
- Property Pane
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/flowlayout.html b/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/flowlayout.html
deleted file mode 100644
index 00771d145..000000000
--- a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/flowlayout.html
+++ /dev/null
@@ -1,72 +0,0 @@
-
-
-
-
- Swing FlowLayout
-
-
-
-
-
Swing FlowLayout
-
-
-
A FlowLayout arranges components in a directional flow, much
- like lines of text in a paragraph. FlowLayouts are typically used
- to arrange buttons in a panel. It arranges buttons horizontally until no
- more buttons fit on the same line. The line alignment is determined by
- the align property.
Select FlowLayout from the Layouts palette and
- drop it on a JFrame or JPanel
-
-
-
-
-
-
-
Graphical feedback is provided for all drop and move
- interactions
-
-
-
-
-
-
-
-
Horizontal and vertical gaps can be specified using the
- Property Pane
-
-
-
-
-
-
-
Horizontal alignment can be specified using the
- Property Pane
-
-
-
-
-
-
-
-
Graphical Feedback
-
-
When moving a widget or adding a new widget, the current drop
- point is highlighted in red
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/gridlayout.html b/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/gridlayout.html
deleted file mode 100644
index 941f6d37c..000000000
--- a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/gridlayout.html
+++ /dev/null
@@ -1,81 +0,0 @@
-
-
-
-
- Swing GridLayout
-
-
-
-
-
Swing GridLayout
-
-
-
The GridLayout class is a layout manager that lays out a
- container's components in a rectangular grid. The container is divided
- into equal-sized rectangles, and one component is placed in each
- rectangle. When both the number of rows and the number of columns have
- been set to non-zero values, either by a constructor or by the
- setRows and setColumns methods, the number of columns
- specified is ignored. Instead, the number of columns is determined from
- the specified number of rows and the total number of components in the
- layout. So, for example, if three rows and two columns have been
- specified and nine components are added to the layout, they will be
- displayed as three rows of three columns. Specifying the number of
- columns affects the layout only when the number of rows is set to zero.
Select GridLayout from the Layouts palette and
- drop it on a JFrame or JPanel
-
-
-
-
-
-
-
Graphical feedback is provided for all drop and move
- interactions
-
-
-
-
-
-
-
-
Horizontal and vertical gaps can be specified using the
- Property Pane
-
-
-
-
-
-
-
-
The number of columns and rows can be specified using the
- Property Pane
-
-
-
-
-
-
-
-
Graphical Feedback
-
-
When moving a widget or adding a new widget, the current drop
- point is highlighted in red
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/grouplayout.html b/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/grouplayout.html
deleted file mode 100644
index f81c9aa30..000000000
--- a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/grouplayout.html
+++ /dev/null
@@ -1,165 +0,0 @@
-
-
-
-
-
- Swing GroupLayout
-
-
-
-
-
Swing GroupLayout
-
GroupLayout is a LayoutManager that hierarchically groups components
-in order to position them in a Container. GroupLayout is intended for use
-by builders, but may be hand-coded as well. Grouping is done by instances of the
-Group class. GroupLayout supports two types of groups. A
-sequential group positions its child elements sequentially, one after another. A
-parallel group aligns its child elements in one of four ways.
-
-Each group may contain any number of elements, where an element is a Group,
-Component, or gap. A gap can be thought of as an invisible component with
-a minimum, preferred and maximum size. In addition GroupLayout supports a
-preferred gap, whose value comes from LayoutStyle.
-
-Elements are similar to a spring. Each element has a range as specified by a
-minimum, preferred and maximum. Gaps have either a developer-specified range, or
-a range determined by LayoutStyle. The range for Components is determined
-from the Component's getMinimumSize, getPreferredSize and
-getMaximumSize methods. In addition, when adding Components you may specify
-a particular range to use instead of that from the component. The range for a
-Group is determined by the type of group. A ParallelGroup's range is
-the maximum of the ranges of its elements. A SequentialGroup's range is
-the sum of the ranges of its elements.
-
-GroupLayout treats each axis independently. That is, there is a group
-representing the horizontal axis, and a group representing the vertical axis.
-The horizontal group is responsible for determining the minimum, preferred and
-maximum size along the horizontal axis as well as setting the x and width of the
-components contained in it. The vertical group is responsible for determining
-the minimum, preferred and maximum size along the vertical axis as well as
-setting the y and height of the components contained in it. Each Component must
-exist in both a horizontal and vertical group, otherwise an
-IllegalStateException is thrown during layout, or when the minimum,
-preferred or maximum size is requested.
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/jgoodies_formlayout.html b/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/jgoodies_formlayout.html
deleted file mode 100644
index ffa29c786..000000000
--- a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/jgoodies_formlayout.html
+++ /dev/null
@@ -1,344 +0,0 @@
-
-
-
-
- JGoodies Form Layout
-
-
-
-
-
JGoodies FormLayout
-
-
-
JGoodies FormLayout is a powerful, flexible and precise
- general purpose layout manager. It aligns components vertically and
- horizontally in a dynamic rectangular grid of cells, with each component
- occupying one or more cells. A whitepaper about the FormLayout
- available online.
- To use FormLayout you first define the grid by specifying the
- columns and rows. In a second step you add components to the grid. You
- can specify columns and rows via human-readable String descriptions or
- via arrays of ColumnSpec and RowSpec instances. Each
- component managed by a FormLayout is associated with an instance
- of CellConstraints. The constraints object specifies where a
- component should be located on the form's grid and how the component
- should be positioned. In addition to its constraints object the
- FormLayout also considers each component's minimum and preferred
- sizes in order to determine a component's size.
Note that JGoodies FormLayout support is only
- available in the Professional version of the product.
- This layout also requires the use of the JGoodies FormLayout jar file
- (forms-1.0.6.jar or higher).
Select JGoodies FormLayout from the Layouts palette and
- drop it on a JFrame or JPanel
-
-
-
-
-
-
-
The JGoodies FormLayout jar file (forms-1.1.0.jar) will automatically be added
- to your project and the classpath adjusted
-
Graphical feedback is provided for all column, row and cell
- interactions
-
Column and row properties may be changed via a popup menu or
- property dialog
-
Convert existing layouts (null, GridBagLayout, etc.) to
- JGoodies
- FormLayout with intelligent column, row and gap creation
-
-
-
-
-
-
-
Automatically add gaps when adding new columns or rows
-
-
Popup Header Menu
-
-
Right-click on the header area to access the popup header menu
-
-
-
-
-
-
-
Insert new columns or rows before the current column or row
-
Add a new column or row at the end of the current list
-
Delete entire columns or rows or just their widget contents
-
Set the column alignment to left, right, center or fill
-
Specify that the column or row should grow to fill the
- available space
-
Group or ungroup columns or rows
-
Set the sizing spec that should be used for the column or row
- (various column, row and gap types are available)
-
Edit the properties of the current column or row
-
-
-
Graphical Feedback
-
-
When moving a widget or adding a new widget, open cells are
- highlighted green while populated cells are highlighted red and
- insertion points are highlighted in yellow
-
-
-
-
-
-
Phantom drop point to the right and below the current cells
- will create new columns, rows and gaps as needed
-
-
-
-
-
-
The currently selected cell shows its column and row spanning
- handles and alignment handles
-
-
-
-
Set the alignment of a cell using its popup alignment menu or the
- toolbar
-
-
-
-
-
-
-
-
-
-
Right-click on a column to set its grow property
-
-
-
-
-
-
-
Grouped columns and rows are color highlighted to indicate
- which are in the same group
-
-
-
-
-
-
-
-
Column and row sizing handles make it easy to set the size
- of a column or row
-
-
-
-
-
-
-
-
-
-
-
Reorder columns and rows by dragging them (with their
- associated gap columns or rows)
-
-
-
-
-
-
-
-
-
Column and rows borders are indicated with gray lines
-
-
-
-
-
-
-
Interactive column and row spanning feedback is provided
-
-
-
-
-
-
-
Full keyboard support for quickly changing alignment values
-
-
-
-
-
Cells
-
-
-
D
-
-
default horizontal
-
-
-
Shift+D
-
-
default vertical
-
-
-
F
-
-
fill horizontal
-
-
-
Shift+F
-
-
fill vertical
-
-
-
L, C, R
-
-
left/center/right for horizontal
-
-
-
T, M, B
-
-
top/middle/bottom for vertical
-
-
-
-
Column & Row Editing
-
-
Double click on a column or row to access its property
- dialog
-
Switch between columns and rows using the arrow buttons
-
-
-
-
-
-
Select from any of the predefined column or gap templates
-
-
-
-
-
-
-
-
Set the column or row alignment
-
Specify the resize behavior and the relative weights of each
- column or row
-
Set the size of the column or row
-
Specify a constant size in a variety of units
-
Specify minimum and maximum sizes
-
-
-
-
-
-
-
-
-
-
Floating layout assistant for constraints
-
-
-
-
-
-
-
-
Open the Columns or Rows editing dialog from the
- Property Pane or the right-click context menu of the panel.
-
-
-
-
-
-
-
-
Insert or add new columns and rows
-
Open the property dialog for an individual column or row
Control whether automatic grab is used for text widgets,
- comboboxes, tables, etc.
-
-
-
-
-
-
-
-
Control whether labels are automatically right-aligned when
- next to a text widget
-
-
-
-
-
-
-
Source Code
- Generation & Parsing
-
-
Intelligently convert existing layouts (null, GridBagLayout, etc.) to
- JGoodies
- FormLayout with column, row and gap creation
-
Generated code will use predefined FormFactory constants as
- necessary
-
Parser can understand reused CellConstraint objects
-
Parser supports all CellConstraint styles
-
Creation methods intended for use by humans
- CellConstraints cc = new CellConstraints();
- cc.xy(2, 1); // second col, first row
- cc.xy(2, 1, "right, bottom"); // aligned to right and bottom
- cc.xy(2, 1, "r, b"); // abbreviated alignment
- cc.xywh(2, 1, 4, 3); // spans 4 cols, 3 rows
- cc.xywh(2, 1, 4, 3, "right, bottom");
- cc.xywh(2, 1, 4, 3, "r, b");
-
-
Constructors intended for builders
- new CellConstraints(); // first col, first row
- new CellConstraints(2, 1);
- new CellConstraints(2, 1, 4, 3);
- new CellConstraints(2, 1, CellConstraints.RIGHT,
- CellConstraints.BOTTOM);
-
-
Constructors intended for building UIs from XML
- CellConstraints cc = new
- CellConstraints();
- new CellConstraints("2, 1");
- new CellConstraints("2, 1, r, b");
- new CellConstraints("2, 1, 4, 3");
- new CellConstraints("2, 1, 4, 3, r, b");
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/miglayout.html b/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/miglayout.html
deleted file mode 100644
index 64b82d085..000000000
--- a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/miglayout.html
+++ /dev/null
@@ -1,314 +0,0 @@
-
-
-
-
- MiG Layout
-
-
-
-
-
MiGLayout
-
-
-
-
-
-
-
MiGLayout is the most versatile and
- flexible Swing and SWT Layout Manager for Java, yet it is very
- easy to learn and use. It is using String or API
- type-checked constraints to format the layout. MiGLayout
- can produce flowing, grid based, absolute (with links), grouped
- and docking layouts. You will never have to switch to another
- layout manager ever again! MiGLayout is created to be to
- manually coded layouts what Matisse/GroupLayout is to IDE
- supported visual layouts.
-
-
-
Note that MiGLayout support is only
- available in the Professional version of the product.
- This layout also requires the use of the MiGLayout jar file
- (miglayout-3.6.jar or higher).
Select MiGLayout from the Layouts palette and
- drop it on a JFrame or JPanel
-
-
-
-
-
-
-
The MiGLayout jar file (miglayout-3.6.jar) will automatically be added
- to your project and the classpath adjusted
-
Graphical feedback is provided for all column, row and cell
- interactions
-
Column and row properties may be changed via a popup menu or
- property dialog
-
Convert existing layouts (null, GridBagLayout, etc.) to
- MiGLayout with intelligent column and row creation
-
-
-
-
-
-
Popup Header Menu
-
-
Right-click on the header area to access the popup header menu
-
-
-
-
-
-
-
Insert new columns or rows before the current column or row
-
Add a new column or row at the end of the current list
-
Delete entire columns or rows or just their widget contents
-
Set the column alignment to left, right, center or fill
-
Specify that the column or row should grow to fill the
- available space
-
Set columns and rows to default or preferred sizes
-
Edit the properties of the current column or row
-
-
-
Graphical Feedback
-
-
When moving a widget or adding a new widget, open cells are
- highlighted green while populated cells are highlighted red and
- insertion points are highlighted in yellow
-
-
-
-
-
-
Phantom drop point to the right and below the current cells
- will create new columns and rows as needed
-
-
-
-
-
-
The currently selected cell shows its column and row spanning
- handles and alignment handles
-
-
-
-
Set the alignment of a cell using its popup alignment menu or the
- toolbar
-
-
-
-
-
-
-
-
-
-
Right-click on a column to set its grow property
-
-
-
-
-
-
-
Column and row sizing handles make it easy to set the size
- of a column or row
-
-
-
-
-
-
-
-
-
-
-
Reorder columns and rows by dragging them
-
-
-
-
-
-
-
-
-
Column and rows borders are indicated with gray lines
-
-
-
-
-
-
-
Interactive column and row spanning feedback is provided
-
-
-
-
-
-
-
Split cells horizontally or vertically
-
-
-
-
-
-
-
Full keyboard support for quickly changing alignment values
-
-
-
-
-
Cells
-
-
-
D
-
-
default horizontal
-
-
-
Shift+D
-
-
default vertical
-
-
-
F
-
-
fill horizontal
-
-
-
Shift+F
-
-
fill vertical
-
-
-
L, C, R
-
-
left/center/right for horizontal
-
-
-
T, M, B
-
-
top/middle/bottom for vertical
-
-
-
-
Column, Row & Cell Editing
-
-
Double click on a column or row to access its property
- dialog
-
Switch between columns and rows using the arrow buttons
-
-
-
-
-
-
Enter arbitrary specifications into the Specification field
-
Set the column or row alignment
-
Specify the resize behavior and the relative weights of each
- column or row
-
Set the minimum, maximum and preferred size of the column or row
-
-
-
-
-
-
-
Floating layout assistant for cell constraints
-
-
-
-
-
-
-
-
Edit individual constraint properties for each widget in the
- Property Pane or the right-click context menu of the
- widget..
-
-
-
-
-
-
-
Click the "..." button to specify an arbitrary cell constraint
- specification (such as docking)
Control whether automatic grab is used for text widgets,
- comboboxes, tables, etc.
-
-
-
-
-
-
-
-
Control whether labels are automatically right-aligned when
- next to a text widget
-
-
-
-
-
-
-
Source Code
- Generation & Parsing
-
-
Intelligently convert existing layouts (null, GridBagLayout, etc.) to
- MiGLayout with column and row creation
-
Generated code will use string-based constants
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/springlayout.html b/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/springlayout.html
deleted file mode 100644
index a3ff8edaf..000000000
--- a/org.eclipse.wb.swing.doc.user/html/layoutmanagers/swing/springlayout.html
+++ /dev/null
@@ -1,112 +0,0 @@
-
-
-
-
-
- Swing SpringLayout
-
-
-
-
-
Swing SpringLayout
-
SpringLayout class that implements an constraint-based layout manager. With
-constraint-based layout, you have independent control over the sizing behavior
-of each of the four sides of a widget. The top, bottom, left, and right sides
-can be independently attached to the sides of the parent container or the sides
-of any sibling widget within the same container using either fixed or relative
-offsets. This proves to be surprisingly powerful and can be used to emulate
-almost any of the other layout managers. The SpringLayout class is very simple
-and only specifies the margins of the container.
Select SpringLayout from the Layouts palette and
- drop it on a JFrame or JPanel
-
-
-
-
-
-
-
Graphical feedback is provided for all widget size and
- position operations
-
-
-
-
-
-
-
-
Graphical Feedback
-
-
Position and size widgets using SpringLayout constraints
-
-
-
-
-
-
-
-
Align widgets horizontally and vertically
-
-
-
-
-
-
-
-
Indent widgets intelligently
-
-
-
-
-
-
-
-
Align widgets to margins
-
-
-
-
-
-
-
-
-
Anchor widgets to the left, right or both sides
-
-
-
-
-
-
-
-
-
Anchor widgets to the top, bottom or both sides
-
-
-
-
-
-
-
-
-
Set anchors via popup context menus
-
-
-
-
-
-
-
-
Align and center widgets using toolbar
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/palettes/swing_palette.html b/org.eclipse.wb.swing.doc.user/html/palettes/swing_palette.html
deleted file mode 100644
index 6f4b59ebb..000000000
--- a/org.eclipse.wb.swing.doc.user/html/palettes/swing_palette.html
+++ /dev/null
@@ -1,270 +0,0 @@
-
-Swing Designer Palette
-
-
-
-
-
-
-
-
-
Swing Designer Palette
-
Swing Designer provides the following palette for creating Swing
- applications.
-
The palette may be fully configured using the
- Palette Manager.
-
-
-
-
-
-
-
-
-
-
JPanel - A generic lightweight container.
-
JScrollPane
-- Provides a scrollable view of a lightweight component. A JScrollPane
-manages a viewport, optional vertical and horizontal scroll bars, and
-optional row and column heading viewports.
-
JSplitPane
-- JSplitPane is used to divide two (and only two) Components. The two
-Components are graphically divided based on the look and feel
-implementation, and the two Components can then be interactively
-resized by the user.
-
JTabbedPane - A component that lets the user switch between a group of components by clicking on a tab with a given title and/or icon.
-
JToolBar - A component that is useful for displaying commonly used Action's or controls.
-
JDesktopPane - A container used to create a multiple-document interface or a virtual desktop.
-
JInternalFrame
-- A lightweight object that provides many of the features of a native
-frame, including dragging, closing, becoming an icon, resizing, title
-display, and support for a menu bar.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Absolute Layout - A absolute layout displays components with specified bounds.
-
- FlowLayout
-- A flow layout arranges components in a left-to-right flow, much like
-lines of text in a paragraph. Flow layouts are typically used to
-arrange buttons in a panel. It will arrange buttons left to right until
-no more buttons fit on the same line.
-
BorderLayout- A border layout lays out a container, arranging and resizing its
-components to fit in five regions: north, south, east, west, and
-center. Each region may contain no more than one component.
-
- GridLayout
-- The GridLayout class is a layout manager that lays out a container's
-components in a rectangular grid. The container is divided into
-equal-sized rectangles, and one component is placed in each rectangle.
-
GridBagLayout
-- The GridBagLayout class is a flexible layout manager that aligns
-components vertically and horizontally, without requiring that the
-components be of the same size. Each GridBagLayout object maintains a
-dynamic, rectangular grid of cells, with each component occupying, one
-or more cells.
-
- CardLayout
-- A CardLayout object is a layout manager for a container. It treats
-each component in the container as a card. Only one card is visible at
-a time, and the container acts as a stack of cards. The first component
-added to a CardLayout object is the visible component when the
-container is first displayed.
-
BoxLayout
-- A layout manager that allows multiple components to be laid out
-either vertically or horizontally. The components will not wrap so, for
-example, a vertical arrangement of components will stay vertically
-arranged when the frame is resized.
-
FormLayout -
- JGoodies
- FormLayout is a powerful, flexible and precise general
- purpose layout manager. It aligns components vertically and
- horizontally in a dynamic rectangular grid of cells, with each
- component occupying one or more cells.
-
SpringLayout - A SpringLayout lays out the children of its associated container according to a set of constraints for each side.
-
GroupLayout - GroupLayout mixes grid layout and free form
- layout.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Horizontal Box - Creates a panel that uses an implicit
- horizontal
- BoxLayout.
-
Vertical Box - Creates a panel that uses an implicit
- vertical BoxLayout.
-
Horizontal strut - Creates an invisible, fixed-width
- component .
-
Vertical strut - Creates an invisible, fixed-height
- component .
-
Horizontal glue - Creates a horizontal glue component .
-
Vertical glue - Creates a vertical glue component .
-
Rigid area - Creates an invisible component that's always the specified
- size .
-
Glue - Creates an invisible glue component .
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
JLabel
-- A display area for a short text string or an image, or both. A label
-does not react to input events. As a result, it cannot get the keyboard
-focus. A label can, however, display a keyboard alternative as a
-convenience for a nearby component that has a keyboard alternative but
-can't display it.
-
JTextField - A lightweight component that allows the editing of a single line of text.
-
JComboBox
-- A component that combines a button or editable field and a drop-down
-list. The user can select a value from the drop-down list, which
-appears at the user's request. If you make the combo box editable, then
-the combo box includes an editable field into which the user can type a
-value.
-
JButton - An implementation of a "push" button.
-
JCheckBox
-- An implementation of a check box -- an item that can be selected or
-deselected, and which displays its state to the user. By convention,
-any number of check boxes in a group can be selected.
-
JRadioButton
-- An implementation of a radio button -- an item that can be selected
-or deselected, and which displays its state to the user. Used with a
-ButtonGroup object to create a group of buttons in which only one
-button at a time can be selected.
-
JToggleButton
-- An implementation of a two-state button -- an item that can be
-selected or deselected, and which displays its state to the user.
-
JTextArea - A JTextArea is a multi-line area that displays plain text.
-
JFormattedTextField - A lightweight component that allows the editing of a single line of text using a predefined mask.
-
JPasswordField
-- A lightweight component that allows the editing of a single line of
-text where the view indicates something was typed, but does not show
-the original characters.
-
JTextPane - A text component that can be marked up with attributes that are represented graphically.
-
JEditorPane - A text component to edit various kinds of content.
-
JSpinner - A lightweight component that allows the lets the user select a number or an object value from an ordered sequence.
-
JList - A component that allows the user to select one or more objects from a list.
-
JTable - The JTable is used to display and edit regular two-dimensional tables of cells.
-
JTable on JScrollPane - A JTable placed within a
- JScrollPane.
-
Table model column - A JTable model column.
-
JTree - A control that displays a set of hierarchical data as an outline.
-
JProgressBar
-- A component that, by default, displays an integer value within a
-bounded interval. A progress bar typically communicates the progress of
-some work by displaying its percentage of completion and possibly a
-textual display of this percentage.
-
JScrollBar - An
-implementation of a scrollbar. The user positions the knob in the
-scrollbar to determine the contents of the viewing area. The program
-typically adjusts the display so that the end of the scrollbar
-represents the end of the displayable contents, or 100% of the contents.
-
JSeparator - A horizontal or vertical line used to separate other controls.
-
JSlider
-- A component that lets the user graphically select a value by sliding
-a knob within a bounded interval. The slider can show both major tick
-marks and minor tick marks between them. The number of values between
-the tick marks is controlled with setMajorTickSpacing and
-setMinorTickSpacing.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
JMenuBar - A menu bar.
-
JPopupMenu - A popup menu.
-
JMenu - Either a pull-down or cascaded menu.
-
JMenuItem - A simple menu item.
-
JCheckBoxMenuItem - A checkbox menu item.
-
JRadioButtonMenuItem - A radio button menu item.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Panel
-- Panel is the simplest container class. A panel provides space in
-which an application can attach any other component, including other
-panels.
-
Canvas - A Canvas component represents a blank
- rectangular area of the screen onto which the application can
- draw or from which the application can trap input events from
- the user.
-
ScrollPane - A container class which implements automatic horizontal and/or vertical scrolling for a single child component.
-
Button - This class creates a labeled button. The application can cause some action to happen when the button is pushed.
-
Label
-- A Label object is a component for placing text in a container. A
-label displays a single line of read-only text. The text can be changed
-by the application, but a user cannot edit itdirectly.
-
Checkbox - A check box is a graphical component that can be in either an
- "on" (true) or "off" (false) state. Clicking on a check box changes its state from
- "on" to "off", or from "off" to
- "on".
-
Choice - The Choice class presents a pop-up menu of choices. The current choice is displayed as the title of the menu.
-
List
-- The List component presents the user with a scrolling list of text
-items. The list can be set up so that the user can choose either one
-item or multiple items.
-
Scrollbar - The
-Scrollbar class embodies a scroll bar, a familiar user-interface
-object. A scroll bar provides a convenient means for allowing a user to
-select from a range of values.
-
TextField - A TextField object is a text component that allows for the editing of a single line of text.
-
TextArea - A TextArea object is a multi-line region that displays text. It can be set to allow editing or to be read-only.
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/preferences/swing/index.html b/org.eclipse.wb.swing.doc.user/html/preferences/swing/index.html
deleted file mode 100644
index 53eda83d8..000000000
--- a/org.eclipse.wb.swing.doc.user/html/preferences/swing/index.html
+++ /dev/null
@@ -1,56 +0,0 @@
-
-Preferences - Swing
-
-
-
-
Preferences - Swing
-
-
-
Here is the list of
- Swing Designer preference pages:
These preferences control the default form size used for any window or
- dialog created by Swing Designer.
Highlight containers without
- borders
-
This preference determines whether Swing Designer draws a dotted
- rectangle around borderless JPanels.
-
Show text in
- components tree
-
This preference determines whether the text label of a widget (like a
- button, label, etc.) is shown next to the widget's name in the
- Component Tree.
-
-
-
Show important properties dialog on
- component adding
-
This preference controls whether the important properties dialog is
- shown whenever a new widget is created. The important properties dialog
- provides access to the widget's name, text and icon properties and style
- settings.
-
Automatically activate direct edit
- on component adding
-
This preference controls whether
- direct edit mode is automatically
- invoked when a new component is added to the window. When this option is
- enabled, it makes it easy to immediately set the text label on a widget
- as soon as it is created.
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_absolute.html b/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_absolute.html
deleted file mode 100644
index 2e95a05fe..000000000
--- a/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_absolute.html
+++ /dev/null
@@ -1,47 +0,0 @@
-Preferences - Swing > Layouts > Absolute
-
-
Preferences - Swing > Layouts > Absolute
-
-
-
This page is used to control various
- Swing > Layouts > Absolute options.
-
- Use 'Free' component placement style
-
This preference determines whether free mode is used for
- aligning widgets. Free mode uses widget snapping similar to that used
- for GroupLayout.
-
-
- Component Gaps
-
This preference determines what default gaps are used between
- components in free mode.
-
- Container Gaps
-
This preference determines what default gaps are used between
- components and their containers in free mode.
-
- Apply 'grid' creation flow
-
This preference determines whether the creation order of the widgets
- will be adjusted to reflect their positions in a left-to-right,
- top-to-bottom grid flow. This will affect the default tab order.
- Use Grid Snapping
-
This preference determines whether grid mode is used for aligning
- widgets. Grid mode uses a user customizable snapping grid.
-
-
Grid Step
-
This preference determines the grid step used in grid mode.
-
-
- Display Grid
-
This preference determines whether the grid is displayed in grid mode.
-
-
- Display location/size hints
-
This preference determines whether location and size
- hints are shown when moving or sizing widgets.
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_code_generation.html b/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_code_generation.html
deleted file mode 100644
index 6c6b89899..000000000
--- a/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_code_generation.html
+++ /dev/null
@@ -1,198 +0,0 @@
-
-Preferences - Swing > Code Generation
-
-
-
-
Preferences - Swing > Code Generation
-
-
-
Use the existing creation style when it can be deduced
-
This preference determines whether Swing Designer attempts to use the
- existing code creation style already in a file to generate code.
- Swing Designer checks a file when it is opened in the editor to see if one
- style or the other is used.If only one of the styles is being used
- in a file, it will continue generating code in that style, regardless of
- what the other code generation settings.If no style is detected (no controls
- have been created yet) or if more than one style is detected, the
- Swing Designer will generate code as specified in the other
- settings.
-
- Method name for new statements
-
This preference determines in which method components will be created by default
- (in the event that a suitable method has not already be
- defined for the current class). If the method does not exist, it will be
- created and a call to it added to the constructor for the class. Various
- default choices are provided to match the code generation patterns of
- other GUI builders.
Default code generation settings
-
Swing Designer supports a wide variety of code generation styles
- and can emulate most other Java GUI builders including NetBeans,
- JBuilder, the Eclipse Visual Editor, etc. Choose a
- Variable
- Generation style (Local,
- Field, Initialized Field or
- Lazy) and a Statement Generation style (Flat or
- Block). Many of the styles have additional options that can be set.
- Once any combination of settings is selected, you can see a preview of
- that code generation style in the Preview pane.
- In the Local variable generation style, each component is
- assigned to a unique local variable and initialized at the point of
- declaration. An option is provided to declare each variable as final.
- Note that component types marked as As Field on the
- Variables > Type
- Specific preference page will always be assigned to fields.
- In the Field generation style, each component is
- assigned to a unique field and initialized at the point where it is
- first used. An option is provided to prefix each field reference with
- this.
- In the Initialized Field generation style, each component is
- assigned to a unique field and initialized at the point at the point of
- declaration. An option is provided to prefix each field reference with
- this.
- In the Lazy generation style, each component is created in its
- own unique getXXX() method. An option is provided to set the
- visibility modifier to private, package private,
- protected or public.
In flat mode, each component is created in the same scope at
- the same indentation level. An option is provided to prefix the creation
- of each component with either a blank line or a comment.
This page is used to control various
- Swing > Code Generation > Event Handler options.
-
Event code generation
-
This preference determines how event handlers are generated. The first
- option, Create anonymous class, generates an anonymous adapter
- class located inline with the widget definition. For example:
-
The second option, Create inner class, generates an adapter
- class as an inner class. Options are provided to add the inner class at
- the beginning or end of the class as well as specify the pattern used to
- name the inner class. For example:
-
The pattern can include the template variables (names enclosed between
- "${" and "}") shown below. Capitalizing the name of any variable will cause
- the value of the variable to be capitalized before it is inserted into the
- resulting text.
-
component_name - the name of the component to which the
- handler is being attached
-
component_class_name - the name of the class of the component
- to which the handler is being attached
-
listener_name - the name of the event being handled
-
listener_className - the name of the event listener
-
-
The third option, Implement listener interface in parent class,
- adds the the listener interface to the parent class and adds the
- appropriate methods to the class definition. For example:
-
This preference determines whether the text field below it is
-enabled.Now whenever an event
-handler is added, a method stub is created with the name given in the text
-field.A line of code is also added to
-the event handler which calls the newly created method.If you move your mouse over the text field,
-a tool tip will appear which gives you information on how to specify the names
-of the method stubs generated.
-
Use this field to change the pattern used to generate the name of the
- method that will be invoked from within the event handler. The pattern can
- include the template variables (names enclosed between "${" and "}") shown
- below. Capitalizing the name of any variable will cause the value of the
- variable to be capitalized before it is inserted into the resulting text.
-
component_name - the name of the component to which the
- handler is being attached
-
component_class_name - the name of the class of the component
- to which the handler is being attached
-
event_name - the name of the event being handled")
-
-
Delete stub event handler methods on component delete
-
This preference determines whether handler methods associated with a
- component are deleted when the component is deleted.
Declare
- parameters in event handlers as 'final'
-
This preference determines whether 'final' is added to the parameters
- in event handlers.
Show icon decorator for components with events
-
This preference controls whether components with event handlers are shown with
- an icon decorator.
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_jgoodies_formlayout.html b/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_jgoodies_formlayout.html
deleted file mode 100644
index 346f01f53..000000000
--- a/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_jgoodies_formlayout.html
+++ /dev/null
@@ -1,27 +0,0 @@
-
-Preferences - Swing > JGoodies FormLayout
-
-
-
-
This page is used to control various
- Swing > Layouts > JGoodies FormLayout options.
-
Use automatic horizontal/vertical grab
-
This preference controls whether new text-oriented widgets (JText,
- JComboBox, etc.) are set to grab horizontally when they are added
- to the window and whether new JTable and JTree widgets are
- set to grab horizontally and vertically when they are added to the
- window.
-
-
- Automatically align right Label-like components before Text components
-
This preference controls whether JLabels should be right aligned when
- they are to the left of a JText or JComboBox widget.
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_layouts.html b/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_layouts.html
deleted file mode 100644
index fa7cf5069..000000000
--- a/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_layouts.html
+++ /dev/null
@@ -1,37 +0,0 @@
-
-Preferences - Swing > Layouts
-
-
-
-
Preferences - Swing > Layouts
-
-
-
This page is used to control various
- Swing > Layouts options.
-
Default layout manager
-
This preference controls the default layout manager that Swing Designer uses
- for any new frame or panel. The default is to use the implicit layout
- manager already in effect for each container (e.g., BorderLayout for JFrames
- and FlowLayout for JPanels).
-
Layouts to use
-
This preference controls the layouts which can be selected in the
- default layout manager and also which layouts are available in the
- Design editor page. If a layout is unchecked that is currently set
- as default layout, the selection in the default layout manager control
- is cleared, with the implict layout being used as default again.
-
Containers automatically use layout manager type of parent
-
This preference determines whether new panels will use the layout
- manager of their parent's by default.
Create variable for Layout
- using pattern
-
This preference determines what pattern will be used to generate layout
- variables. The following styles are supported:
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_lookandfeel.html b/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_lookandfeel.html
deleted file mode 100644
index e633755ad..000000000
--- a/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_lookandfeel.html
+++ /dev/null
@@ -1,58 +0,0 @@
-
-Preferences - Swing > LookAndFeel
-
-
-
-
Preferences - Swing > LookAndFeel
-
-
-
-
This page is used to control various
- Swing > LookAndFeel options.
-
Any look and feel types listed on this page will show up in Designer's
- toolbar in the look and feel drop down list.
-
-
-
-
-
-
-
Windows
-
-
-
-
Motif
-
-
-
-
-
-
Metal
-
-
-
-
Liquid
-
-
-
-
-
You can add more looks by clicking on the
- Add button and specifying the look you want to add in the Add
- LookAndFeel dialog that appears.
- To edit a look, select it and click on Edit. To
- remove a look, select it click on Remove. To set a look as the
- default look used in Designer, select the look and click on the Set Default button.
-
-
Apply chosen LookAndFeel in main() method
-
This preference determines whether Designer adds code to set the
- selected Look and Feel in the main() method. For example:
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_miglayout.html b/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_miglayout.html
deleted file mode 100644
index 17619221a..000000000
--- a/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_miglayout.html
+++ /dev/null
@@ -1,28 +0,0 @@
-
-Preferences - Swing > MiGLayout
-
-
-
-
Preferences - Swing > Layouts > MiGLayout
-
-
-
-
This page is used to control various
- Swing > Layouts > MiGLayout options.
-
Use automatic horizontal/vertical grab
-
This preference controls whether new text-oriented widgets (JText,
- JComboBox, etc.) are set to grab horizontally when they are added
- to the window and whether new JTable and JTree widgets are
- set to grab horizontally and vertically when they are added to the
- window.
-
-
- Automatically align right Label-like components before Text components
-
This preference controls whether JLabels should be right aligned when
- they are to the left of a JText or JComboBox widget.
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_nls.html b/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_nls.html
deleted file mode 100644
index 2f87caba6..000000000
--- a/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_nls.html
+++ /dev/null
@@ -1,28 +0,0 @@
-
-Preferences - Swing > Code Generation > NLS
-
-
-
-
Preferences - Swing > Code Generation > NLS
-
-
-
-
This page is used to control various
- SWT > Code Generation > NLS options.
-
Automatically externalize string properties, if class contains
- externalized properties
-
This preference determines whether Designer will automatically
- externalize the string properties for new widgets as they are added.
- This preference only applies to classes that have already had their
- strings externalized.
Use qualified name in keys
-
This preference determines whether qualified names are used to create
- keys.
Key as value prefix
-
This preference determines what prefix should be used for NLS keys
- directly entered into the property pane.
-
Always visible locales
-
This preference determines what locales should always be listed. This
- should be a comma separated list such as "en, de, ru".
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_variables.html b/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_variables.html
deleted file mode 100644
index 0c36af23e..000000000
--- a/org.eclipse.wb.swing.doc.user/html/preferences/swing/preferences_variables.html
+++ /dev/null
@@ -1,81 +0,0 @@
-
-Preferences - Swing > Code Generation > Variables
-
-
-
-
Preferences - Swing > Code Generation > Variables
-
-
-
This page is used to control various Swing > Code Generation >
- Variables options.
There
-are already several types listed in the table. You can add more types by clicking on the Add button and entering in the
-name of the class you want to add in the dialog box that appears. To remove a type, highlight it in the table
-and click on Remove.
-
-
The
-Default Name column of the table lets you change what variable name is
-initially used when a control of that type is created. To change the default name, simply click in
-the table cell that you wish to modify and type in the name. Press Enter to apply the change or Esc to
-cancel. Any names that are entered must be valid Java identifiers.
-
- The Acronym column of the table lets you specify a short name for
- the type that is used in automatic variable renaming. Any acronyms that
- are entered must be valid Java identifiers.
-
-
The
-As Field column has a checkbox for each table item. If an item's As Field cell is checked, all new controls of that
-type will be created as a field. When a
-control is created as a field, it places the declaration of the control in the
-class outside of any methods.
This preference determines whether component variable
- names are renamed based on the value of the text component. This can be set to
- "Always", "Never" or "For default names". The later means that only
- components that still have their default names will be renamed. Once
- renamed, they will not be renamed again.
Create variable using
- pattern
-
This preference determines what pattern is used when creating a
- new variable name. Available pattern parts are:
-
${class_acronym} - the acronym of the short class name
-
${text} - the value of the text property
-
${class_name} - the short class name
-
${default_name} - the default name of the component
-
-
Process only n words of text value
-
This preference determines how many words from the text component
- are used when generating the new variable name. Use "0" for no
- limit.
This preference determines whether the widget's name is set in the
- widget's name property.
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/properties/property_editor_border.html b/org.eclipse.wb.swing.doc.user/html/properties/property_editor_border.html
deleted file mode 100644
index 84d672884..000000000
--- a/org.eclipse.wb.swing.doc.user/html/properties/property_editor_border.html
+++ /dev/null
@@ -1,230 +0,0 @@
-
-Border Editor
-
-
-
-
-
Border Editor
-
-
-
-
-
-
Click the
- button
-to access the Border Editor and configure a border. Select the border
-type from the drop down list and then choose options unique to that border
-types. Three previews of what the border will look like are shown at the bottom
-of the dialog.
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/properties/property_editor_combobox_model.html b/org.eclipse.wb.swing.doc.user/html/properties/property_editor_combobox_model.html
deleted file mode 100644
index e63f541f5..000000000
--- a/org.eclipse.wb.swing.doc.user/html/properties/property_editor_combobox_model.html
+++ /dev/null
@@ -1,25 +0,0 @@
-
-ComboBox Model Editor
-
-
-
-
-
ComboBox Model Editor
-
-
-
-
-
-
Click the
- button
-to access the ComboBox Model Editor and enter multiple items. Each line
-is treated as a separate list item.
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/properties/property_editor_key_stroke.html b/org.eclipse.wb.swing.doc.user/html/properties/property_editor_key_stroke.html
deleted file mode 100644
index b532d8f92..000000000
--- a/org.eclipse.wb.swing.doc.user/html/properties/property_editor_key_stroke.html
+++ /dev/null
@@ -1,25 +0,0 @@
-
-List Model Editor
-
-
-
-
-
Key Stroke Editor
-
-
-
-
-
-
Click the
- button
-to access the Key Stroke Editor and enter a key stroke combination. Any
-combination of modifiers can be selected as well as a single key code.
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/properties/property_editor_label_for.html b/org.eclipse.wb.swing.doc.user/html/properties/property_editor_label_for.html
deleted file mode 100644
index b3c9c88e1..000000000
--- a/org.eclipse.wb.swing.doc.user/html/properties/property_editor_label_for.html
+++ /dev/null
@@ -1,25 +0,0 @@
-
-List Model Editor
-
-
-
-
-
Label For Editor
-
-
-
-
-
-
Click the
- button
-to access the Label For Editor and select an widget to associate the
-label with.
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/properties/property_editor_list_model.html b/org.eclipse.wb.swing.doc.user/html/properties/property_editor_list_model.html
deleted file mode 100644
index 505db406f..000000000
--- a/org.eclipse.wb.swing.doc.user/html/properties/property_editor_list_model.html
+++ /dev/null
@@ -1,25 +0,0 @@
-
-List Model Editor
-
-
-
-
-
List Model Editor
-
-
-
-
-
-
Click the
- button
-to access the List Model Editor and enter multiple items. Each line
-is treated as a separate list item.
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/properties/property_editor_spinner_model.html b/org.eclipse.wb.swing.doc.user/html/properties/property_editor_spinner_model.html
deleted file mode 100644
index 2783cc278..000000000
--- a/org.eclipse.wb.swing.doc.user/html/properties/property_editor_spinner_model.html
+++ /dev/null
@@ -1,34 +0,0 @@
-
-List Model Editor
-
-
-
-
-
Spinner Model Editor
-
-
-
-
-
-
Click the
- button
-to access the Spinner Model Editor and specify either a list model, number
-or date model. For a list model, you can enter multiple items. Each line
-is treated as a separate list item. For a number model, you can specify the
-number type, an
-initial value, a minimum value, a maximum value, and a step size. For a date
-model, you can specify an initial date, start date, a stop date, and a date
-type. For each
-model, you can test the spinner model using a preview spinner at the bottom of
-the editor.
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/properties/property_editor_table_model.html b/org.eclipse.wb.swing.doc.user/html/properties/property_editor_table_model.html
deleted file mode 100644
index 182712345..000000000
--- a/org.eclipse.wb.swing.doc.user/html/properties/property_editor_table_model.html
+++ /dev/null
@@ -1,27 +0,0 @@
-
-Table Model Editor
-
-
-
-
-
Table Model Editor
-
-
-
-
-
-
Click the
- button
-to access the Table Model Editor and specify the number of columns and
-rows. For each column, the title, type, width, editable and resizable properties
-can be set. Individual cell values can also be set in the editable table in the
-editor.
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/org.eclipse.wb.swing.doc.user/html/properties/property_editor_tree_model.html b/org.eclipse.wb.swing.doc.user/html/properties/property_editor_tree_model.html
deleted file mode 100644
index 777ddec05..000000000
--- a/org.eclipse.wb.swing.doc.user/html/properties/property_editor_tree_model.html
+++ /dev/null
@@ -1,26 +0,0 @@
-
-Tree Model Editor
-
-
-
-
-
Tree Model Editor
-
-
-
-
-
-
Click the
- button
-to access the Tree Model Editor and enter multiple tree items. Each line
-is treated as a separate tree item. Indenting an item makes it a child of the
-item above it.
- Beans and
- 
- Widgets. The filter field above the list can be used to filter the
- list of items. The
- 
- clear button can be used to clear the filter and restore the full list.
- 
- 
- 
- 
- Bind button to open the Create Data Binding dialog. m_groups.group
- contains elements of type PhoneGroup, so select the type
- PhoneGroup and its <EL Expression> property. In the EL
- Expression field, type "${name} ({$personCount})". Note that selecting
- the name property would result in just the name of the group
- being displayed. You can use EL Expressions to create more complex
- results. In this case, we can show the name plus the number of people in
- the group.
- 
- 
- button next to an unbound property will open the
- Create Data
- Binding wizard while clicking the
- 
- 
- 
- 
- 
- 
- Edit button or Edit menu opens the Edit Binding dialog
- where the update strategy, converter and validator may be modified.
- Delete button or Delete menu is used to delete the selected
- bound property while the
- 
- Delete All button or Delete All menu is used to delete all of
- the bound properties.
- Move Up and
- 
- Move Down buttons and menus are used to change the order of the
- bindings while the
- 
- Goto Definition button and menu are used to jump to the generated
- code for the binding.
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
-
-
E
-
-
-
-
-
-
-
-
-
-
- 
-
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
-
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
-
-
-
-
-
-
-
-
-
-
- 
- 
- 
- 
- 
- 
- 
- 
- 
Method name for new statements
- 
- 
- 
- 
- 
button
-to access the Border Editor and configure a border. Select the border
-type from the drop down list and then choose options unique to that border
-types. Three previews of what the border will look like are shown at the bottom
-of the dialog.
- 
- 
