The appearance of a component may be changed with the indication of a Plugin class (a special possibility).
The self compiled JavaBean is selected at run-time, instead of the standard component for the visualization of the representation type.
Figure 55: XUI component - PlugIn
The validation and representation of the data is up to the respective plugin component. A Java interface (visualizer) allows the communication between the rendering engine and the PlugIn component.
The following figure shows the definition of the ā€˛FileDialog"PlugIn.
231
Figure 56: Definition of a PlugIn
(1) Double-click one of the installed PlugIns. The selected class is taken over, and all the configuration options listed under the label ā€˛Constructors".
The PlugIn classes are instantiated with the Java Reflection API. A list of all constructors of this class appears, with a combination of parameter types to be processed by JAXFront. (see section 2.5.3.1). If no constructors are displayed, a Java Default Constructor exists for the selected class.
(2) Select the desired configuration (constructor) with a double-click. All the parameters to be declared are listed.
(3) Fill out the contents of the displayed parameter entries
A precise specification of the parameter types and their expected values is delivered by the JavaDoc of the respective PlugIn class.