Composition of eprint custom printing tools

Eprint custom printing consists of three components: DataSet interface layer, print format designer, and print and publish.

 

Dataset interface layer:
Eprint custom printing and user system interfaces are implemented through datasets, which are the data to be printed by the user. When developing the report module, developers usually execute some SQL statements for query, or generate reports based on the data (including statistical data) required by the end user through some operations. Eprint custom printed dataset refers to the data that is converted into XML format in a certain format, including the data structure and data record. The data structure is like the table structure in a relational database, A data record is a table record in a relational database. The string data that stores data structures and records in a predefined XML node format is a dataset. Format: ZY. xml.
User-Defined Data Set eprint shields the dependency on the database of the user system and the dependency on the result set generated after a single SQL statement is executed.

Print format designer:
The format designer is a "what you see is what you get" visual design interface. You can drag the elements to be printed to the page and set the attributes of the elements, expressions and so on to customize the print formats of various types of reports. The designed format is saved as an XML file for easy format import and export. During the design process, you can print and preview the results so that you can get the print effect instantly. The design interface can be provided to end users, so that end users can adjust the print format in real time.

Print release: 
Eprint custom printing saves the report printing format edited by the print format designer as an XML file. an XML file is called a printing template. Templates of the same type are classified as one type. That is to say, multiple print formats can be designed for the same report. Eprint custom printing can maintain these templates, including adding, modifying, and deleting templates.

Developers can simply execute several functions to integrate the designed print Template into the development system. For example
Printer. Preview ("template ID. xml"); this is the print preview function.
Printer. Print ("template ID. xml"); this is the printing function.