The Java(TM) Client Sample Application views were developed using the Java Visual Editor from WebSphere(R) Studio Application Developer Integration Edition 5.0. The editor may be customized to show the toolkit palette of visual beans to make the development easier.
The following three views are developed:
The panels extend DSEPanel class, which extends DSECoordinatedPanel, and so the panels implement the interface to throw events to the Navigation Controller. See the Desktop documentation for more information. The following types of visual beans have been used to build the views:
Each has a set of properties that give a specific behavior to the bean. The properties customization view looks as follows:
The following properties deserve special mention:
DSE_dataName: This SpTextField property associates the text field with a data field in the operation context. Any data that is entered will be assigned to the context, and any data in context will be displayed in the text field.
DSE_dataNameForList: This property allows the assignment of a data collection to an SpComboBox.
DSE_formatter: This SpTextField property associates a formatter (provided by the toolkit), to the data that is entered in the field.
DSE_type: This SpPushButton property allows you to set a default behavior for the button (for example, Close, OK, Execute, Clear).
DSE_helpId: This property associates an HTML file with the visual bean. At runtime, when a bean is selected and the user types a hot key, the help file will be displayed.
DSE_navigationParameters: This is a set of properties that define how to navigate among views using events that cause another view to be displayed using a particular context. The following is an example of how to set these parameters:
The above image shows the navigation parameters for the Account Statement button that appears on the AccountOperationView.
Note: The DSE_type property of that button is execute_operation. This implies that the operation selected in the Operation Name field (AccountStatementClientOp) will be executed when the button is clicked. All the other parameters tell the Navigation Controller what needs to be done after the operation executes. In the example, the View Name is set to AccountStatementView, as the view that will be opened after executing the operation. The new view will behave as required by the application after the parameters in the Navigation and Link Context to fields have been set.
The Account Operation view is developed using the following steps:
Note: In version 3, the button property DSE_type had to be set to OK for launching an operation (and only one button could be associated with the panel). Now, different buttons can launch different processes.
This sample view has been developed using the following new features of visual beans version 4: