Home >> All >> org >> jfree >> report >> modules >> gui >> [ config Javadoc ]

•	org.jfree.report.modules.gui.config.editor.* (9)	•	org.jfree.report.modules.gui.config.model.* (13)
•	org.jfree.report.modules.gui.config.resources.* (3)	•	org.jfree.report.modules.gui.config.xml.* (2)

• org.jfree.report.modules.gui.config: Javadoc index of package org.jfree.report.modules.gui.config.


Package Samples:

• org.jfree.report.modules.gui.config.xml: The configuration editor provides a gui to write the "jfreereport.properties" file that can be used to configure this library.  
• org.jfree.report.modules.gui.config.editor
• org.jfree.report.modules.gui.config.model
• org.jfree.report.modules.gui.config.resources

Classes:

• BugFixProxyGraphics2D: This documents another sad chapter in Sun's java implementation. The tree cell renderer does not check the clipping of the painted graphics correctly. This bug seems to be related to the TreeCellRenderer's unability to display the defined (and drawn) background of the CellRenderers render component. A first hint of that bug can be found at http://www.cs.cf.ac.uk/Dave/HCI/HCI_Handout_CALLER/node155.html
• ConfigTreeModuleNode: The config tree module node is used to represent a module in the report configuration. Modules collect all task-specific configuration keys and represent a report module from the package manager. It is assumed, that all modules define their keys within the namespace of their package.
• ModuleEditor: The module editor is used to provide a customizable editor component for a JfreeReport module. At the moment, there is only one common module editor known, which provides an on-the-fly editor for all defined properties of the module. Specialized editors may be added in the future.
• ConfigTreeModel: Provides a tree model view for an report configuration. The configuration will be separated into a local and a global part. The local nodes are read from the report's configuration instance, while the global nodes are always read from the global report configuration instance.
• ConfigTreeRenderer: Implements a config tree renderer that fixes some AWT-Graphics problems in conjunction with the clipping. It seems that the AWT-Graphics ignores the clipping bounds for some primitive operations. Clipping is done if the operations are performed on the Graphics2D level.
• ConfigDescriptionModel: This list model implementation collects all config description entries defined in JFreeReport. This model is used to create a configuration key definition; it directly manipulates the metadata for the keys as stored in the config-description.xml file.
• ConfigTreeSectionNode: The section node contains the modules for the given section. There are only two known sections, the global section, which contains all boot-time keys and the local section, which contains all report-local configuration keys.
• EnumConfigDescriptionEntry: The enumeration config description entry represents an configuration key, where users may select a valid value from a predefined list of elements. Such an key will not allow free-form text.
• ConfigEditor: The ConfigEditor can be used to edit the global jfreereport.properties files. These files provide global settings for all reports and contain the system level configuration of JFreeReport.
• ClassConfigDescriptionEntry: A config description entry that describes class name configurations. The specified class in the configuration is forced to be a subclass of the specified base class.
• EnumKeyEditor: The enumeration key editor is used to edit configuration keys, which accept a closed set of values. The possible values are defined in the config-description.
• EditorFactory: The editor factory is used to create a module editor for an given module. Implementors may add their own, more specialized editor components to the factory.
• AbstractConfigTreeNode: An abstract base implementation of the config tree node interface. The implementation provides all base services needed to have an valid TreeNode.
• AbstractKeyEditor: This key editor class is the base class for all key editor components. It provides common services usable for most key editor implementation.
• ConfigDescriptionEditor: The config description editor is used to edit the configuration metadata used in the ConfigEditor to describe the ReportConfiguration keys.
• ConfigDescriptionEntry: A config description entry provides a declaration of a single report configuration key and speicifes rules for the values of that key.
• ConfigEditorPanel: The container component that is responsible for creating and managing the module editor for the currently selected module.
• DefaultModuleEditor: The default module editor provides a simple default implementation to edit all configuration keys for a given module.
• ModuleNodeFactory: The module node factory is used to build the lists of modules and their assigned keys for the ConfigTreeModel.
• ClassKeyEditor: The class key editor is used to edit report configuration keys which take the name of an class as value.
• TextConfigDescriptionEntry: The text config description entry represents an configuration key, where users may enter free-form text.

Home | Contact Us | Privacy Policy | Terms of Service