| Home >> All >> org >> jfree >> report >> modules >> output |
Package Samples:
• org.jfree.report.modules.output.pageable.base.operations: Support for the output targets that are page- and print oriented.
• org.jfree.report.modules.output.pageable.base.pagelayout
• org.jfree.report.modules.output.pageable.base.physicals
• org.jfree.report.modules.output.pageable.base.output
• org.jfree.report.modules.output.pageable.base
• org.jfree.report.modules.output.pageable.pdf
• org.jfree.report.modules.output.pageable.graphics
• org.jfree.report.modules.output.pageable.plaintext
• org.jfree.report.modules.output.support.itext
• org.jfree.report.modules.output.support.pagelayout
• org.jfree.report.modules.output.table.html
• org.jfree.report.modules.output.table.base
• org.jfree.report.modules.output.table.xls
• org.jfree.report.modules.output.table.csv
• org.jfree.report.modules.output.table.rtf
• org.jfree.report.modules.output.xml
• org.jfree.report.modules.output.csv
Classes:
• HtmlFilesystem: The HtmlFilesystem provides an abstraction layer for the various storage methods implemented for the HtmlProducer. DirectoryHtmlFilesystem Writes the generated Html-File and the supplementary data files (images and external Stylesheet definition) into a directory. The data files can be written into a separated data directory. {link StreamHtmlFilesystem} Writes a single generated Html-File into the supplied stream. The Stylesheet is inlined in the html file, no other external data files are generated. Images, which are loaded from an valid URL are included in the file, any other images are ignored. ...
• PlainTextOutputTarget: An outputtarget, that generates plaintext. The text can be enriched with escape sequences for Epson- or IBM-Compatible printers. This target does not support images, shapes or different fonts. The output generation is needle-printer oriented, the pageformat is translated into a text page, graphics coordinates are aligned along the character grid of the text mode. It is assumed that all characters have the same width, proportional printing is not supported. The output mode is defined by supplying a suitable PrinterCommandSet. Depending on the target printer, you can supply several PrinterCommandSets: ...
• TableGrid: The TableGrid is used to collect all table cells and to finally create the TableGridLayout. The TableGrid stores TableCellData elements and collects their boundaries. The CellData-bounds are used to define the positions of the cells of the generated table. The TableGrid has two modes of operation. In the strict layoutmode, all bounds of the cells are used to define the generated cells. The strict layout mode tries to layout the cells in a way, that the generated results nearly equals the printed layout. If strict mode is disabled, only the origin of the TableCellData is used to define the generated ...
• SimplePageLayouter: A simple page layouter. This class replicates the 'old' behaviour of JFreeReport, simple and straightforward. Layout Constraints used: PageHeader, PageFooter: BandStyleSheet.DISPLAY_ON_FIRST_PAGE Defines whether a PageHeader or ~footer should be printed on the first page. PageHeader, PageFooter: BandStyleSheet.DISPLAY_ON_LAST_PAGE Defines whether a PageHeader or ~footer should be printed on the last page. A warning: For the PageHeader this works only if the ReportFooter has a pagebreak before printing. GroupHeader: BandStyleSheet.REPEAT_HEADER Defines whether this GroupHeader should be repeated ...
• HtmlProcessor: The HtmlProcessor handles the initialisation of the report writer and starts and manages the report process. The Html content is not written directly into an OutputStream. As Html-Files are able to use external references to include images and style information, the output target is provided using an abstract HtmlFilesystem. Depending on the implementation, the output is written into a directory, a ZipFile or a single Html-stream. This output target supports the generation of XHTML or HTML4 output. All recent browsers should be able to handle XHTML output. XHTML is standard XML code, so that any ...
• PageLayouter: The baseclass for all PageLayouter. A page layouter is the layoutmanager of an logical page. This layoutmanager is responsible for handling and detecting page breaks, for placing the various Root-Bands (bands that are contained directly in an report) on the page and for the global appeareance of an page (columns, band placement policy etc.) A PageLayouter for an Report is defined by the ReportProperty pageable.layoutManager by setting the classname of the page layouter. The specified class must contain an DefaultConstructor and must be an instance of PageLayouter. All PageLayouter may define a ...
• ReportStateList: The ReportState list stores a report states for the beginning of every page. The list is filled on repagination and read when a report or a page of the report is printed. Important: This list stores page start report states, not arbitary report states. These ReportStates are special: they can be reproduced by calling processPage on the report. Internally this list is organized as a list of WeakReferenceLists, where every WeakReferenceList stores a certain number of page states. The first 20 states are stored in an ordinary list with strong-references, so these states never get GarbageCollected ...
• PhysicalOperation: The base class for an operation that can be applied to an org.jfree.report.modules.output.pageable.base.OutputTarget . These operations are typically added to a org.jfree.report.modules.output.pageable.base.physicals.PhysicalPage in the process of being sent to the output target. Refer to the subclasses for some examples. A sequence of operations can be stored in a org.jfree.report.modules.output.pageable.base.Spool and replayed at any time.
• PDFOutputTarget: An output target for the report engine that generates a PDF file using the iText class library (see http://www.lowagie.com/iText , note that the URL is case-sensitive!). If the system property "org.jfree.report.modules.output.pageable.pdf.PDFOutputTarget.AUTOINIT" is set to "true", the PDF-FontFactory is automatically initialized when this class is loaded. Be aware that embedding many fonts will result in larger files. When using Unicode characters, you will have to adjust the encoding of this target to "Identity-H", to enable horizontal unicode printing. This will result in larger files. The Encoding ...
• TableCellData: Encapsulates cell information, either style information or cell data, and the cell bounds. The cell bounds are used by the TableGridLayout to place the cell into a TableGrid . This class contains all data needed to successfully layout the table grid. The cell style information is dependent on the concrete implementation and not defined here.
• TableGridElement: The Element class encapsulates all TableCellData-object within a single grid cell. When the report is badly designed, cells may overlay. This will cause trouble when the table is printed later, so we do not accept multiple non-background TableCellData objects. TableCellData backgrounds can be combined to create complex background structures. Usually, the cell backgrounds must be merged before the cellbackground can be applied to the generated table. As this is dependent on the table implementation, we do not assume anything here, and just collect all backgrounds in the list.
• HtmlProducer: The TableProducer is responsible for creating the produced Table. After the writer has finished the band layout process, the layouted bands are forwarded into the TableProducer. The TableProducer coordinates the cell creation process and collects the generated TableCellData. The raw CellData objects are later transformed into a TableGridLayout. The generated HTML code is cached and written after the last cell was created, to insert the StyleSheet into the html header.
• CSVTableProcessor: The CSVTableProcessor coordinates the output for the layouted CSV output. The bands are layouted and the layouted contents are printed into the csv-file. For data oriented csv output try the org.jfree.report.targets.csv.CSVProcessor . The used writer is not closed after the processing, the caller is responsible to close the writer. The CellSeparator can be used to alter the separator character, f.i. to create tab-separated files.
• OperationModule: The base class for an operation module. Operation modules can be either specific modules for a certain specialized type of content ("text/plain", for instance) or a module can be a generic handler for a certain group of content ("text/*"). While a generic handler may not be as performant as a specialized handler, that handler may be useful for displaying at least some of the content. todo 090 add support for generic handlers to the operation factory.
• TableWriter: The TableWriter is the content creation function used to collect the cell data. After the layouting is done, the layouted bands are forwarded to the TableProducer. The virtual page has an unlimited size, only when a manual pagebreak is encountered, a new page is started. This can be used to f.i. to create separate sheets in Excel-Workbooks, the detailed semantics depend on concrete implementation of the TableProducer. This writer is not thread-safe.
• ZIPHtmlFilesystem: Similiar to the DirectoryHtmlFilesystem, the generated Html-File and the supplementary data files (images and external Stylesheet definition) into a directory in a ZIP-File. The data files can be written into a separated data directory within the ZIP-File. External referenced content can either be copied into the data directory or could be included as linked content. This behaviour is controled by the copyExternalImages flag.
• TableProducer: The TableProducer is responsible for creating the produced Table. After the writer has finished the band layout process, the layouted bands are forwarded into the TableProducer. The TableProducer coordinates the cell creation process and collects the generated TableCellData. The raw CellData objects are later transformed into a TableGridLayout. This class defines the global contract and provides some helper methods for the implementors.
• CSVTableProducer: The TableProducer is responsible for creating the produced Table. After the writer has finished the band layout process, the layouted bands are forwarded into the TableProducer. The TableProducer coordinates the cell creation process and collects the generated TableCellData. The raw CellData objects are later transformed into a TableGridLayout. This class defines the global contract and provides some helper methods for the implementors.
• ExcelProcessor: A report processor that coordinates the output process for generating Excel files. The Jakarta POI library is used to write files in Excel format. If the property "EnhancedDataFormat" is set to true, this target uses the extended Cell-Data format capabilities of POI 1.10 to format the cell value as numeric or date value. An excel-specific format string can be defined for every element using the element- style key "Excel.CellDataFormat".
• TableCellBackground: Encapsulates all TableCellBackground informations, such as borders and background color. The TableCellBackground contains the format information for the table cells. Background information is used to format the tablecells in the TableWriter . CellBackgrounds can be shared for multiple cells.
• XMLWriter: The XMLWriter is the content creation function used to create the XML content. This implementation does no layouting, the bands and elements are written in the defined order. The xml writer is intended as simple example on how to write OutputFunctions, the XML-code generated is very simple and easy to understand. If you seek complexer XML-Outputs, have a look at the HTML-Writer, this implementation is able to write XHTML output.
• XMLProcessor: The XMLProcessor coordinates the report processing for the XML-Output. This class is responsible to initialize and maintain the XMLWriter, which performs the output process. The XMLProcessor is not intended to produce complex output, it is an educational example. If you want valid xml data enriched with layouting information, then have a look at the HTML-OutputTarget, this target is also able to write XHTMl code.
• PhysicalPage: Represents a physical page. Here comes the last step of production, the bands are transfered from the logical page to the physical page. That page does not know anything specific about bandtypes and how to handle them, is just able to print all that is fed into the page and that's it. It will not decide when to make a pagebreak, logical page is responsible for that. It is a simple operation container ...
• StreamHtmlFilesystem: The StreamHtmlFilesystem is an Implementation for streamed HTML output. The generated content is a single Html-Stream, without any external generated data. The generated HTML Stream has an inline style sheet definition and supports external images. The external images must be loaded from HTTP, HTTPS or FTP sources, generated images or images loaded from the local filesystem are not supported.
• EmptyContentHtmlReferenceData: Stores a marker, that the referenced cell is empty. HTML requires empty cells to be filled with an invisible character, or the cell is ignored. Ignored cells tend to destroy the table layout, so we make sure that every cell has content inside. This reference is used to mark empty external image references, when no external entity was referenced and no external content creation is allowed.
| Home | Contact Us | Privacy Policy | Terms of Service |