Objects and Interfaces for Creating UDOs
The following objects and interfaces are necessary for creating a UDO. Refer to the corresponding class or interface in the Logi JReport Javadoc located at
This is an object provided by the Logi JReport system, and is used to derive a UDO. The JRObjectTemplate contains several predefined properties of the standard Logi JReport Object used to compose a report, including: X, Y, Height and Width. You can add more properties (supported by Logi JReport system) to your own UDO. These properties can be viewed and modified by the Report Inspector at design time.
Note: Only Logi JReport system properties or properties inherited from them can be added, such as JetNumber, JetColor, JetString, and JetEnumeration. See the jet.controls package.
This is another object provided by the Logi JReport system. You will need to define an object inherited from this object, so that you can specify the methods for saving and restoring the UDO object. JRVisiableResult provides methods for saving and restoring UDOs.
If the UDO you define is not used for displaying, that is, it will not appear inside the report result on the screen or on paper, then it can be inherited from the JRObjectResult object.
This is an interface. It takes Logi JReport system's Logi JReport Record as input parameters and produces the UDO's JRObjectResult. A definition of the Logi JReport Record is in the jet.connect package.
This is another interface. It provides a method used for painting the UDO to the report. The report can then be shown on the screen or printed on a printer.
This is an optional interface. If specified, the Logi JReport system will use it to handle interactive events (key events, mouse events, paint, and so on) at design time. If this interface is not implemented, the Logi JReport system will use the default one.
This interface is used when you define a UDO with a value which is calculated based on a group of data.