|
AdmissionJC2 example illustrates a
nice feature which allow you in an interface window to refer a
displayGroup defined in the other interface.
AdmissionJC2 example has two EOSwingInterface: AdmissionJCSwingInterface
and ActivitySwingInterface. (See the image)
It shows as one can built a widget which refer to a displayGroup
defined elsewhere than the current EOSwingInterface, i.e. in
another EOSwingInterface.
Here a snippet from
the ActivitySwingInterface.xml
<table>
<widget>
aTable
</widget>
<displayGroup>
admissionJCSwingInterface.displayGroupActivities
</displayGroup>
<column>
<title>Name</title>
<key>
name
</key>
... ...
where the displayGroup of the aTable
widget is the displayGroupActivities which is defined in the AdmissionJCSwingInterface.xml
file, provided that admissionJCSwingInterface exist in
the ActivitySwingInterface.java as a public instance field of
the AdmissionJCSwingInterface class
Further, one can use as target of <actionListener>
another istance of EOSwingInterface provided that such other
instance is defined as public instance field in the corresponding
java class. To exemplify this, in the ActivitySwingInterface gui
there is a button that call an action defined in
the AdmissionJCSwingInterface class. Here another snippet from
the ActivitySwingInterface.xml
<actionListener>
<widget>
testActionButton
</widget>
<target>
admissionJCSwingInterface
</target>
<action>
testAction
</action>
</actionListener>
where admissionJCSwingInterface
refers to an AdmissionJCSwingInterface public instance field which
have to exist in the ActivitySwingInterface.java
|
