Rendering-Independent Page Layout via Generic Protocol
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current reporting systems lack layout/pagination consistency across different output formats and incur unnecessary computational load due to redundant calculations and handshaking, as each renderer implements its own logic and recalculates layout/pagination for each format, leading to inefficiencies in processing and communication.
Innovation Solution
A rendering architecture that uses a generic protocol to determine layout and pagination rules, allowing these rules to be formatted and processed remotely, reducing parallel processing needs and enabling computation distribution between server and client, while also providing metadata for editability and independent persistability of rendering-independent pages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If each renderer implements its own layout/pagination logic, then each output format can be generated independently, but layout/pagination consistency across formats deteriorates
Solution Approach 1:
The system segments the rendering process into two independent components: layout/pagination calculation (performed once by the report processing module) and format-specific rendering (performed by individual renderers). This separation allows each component to specialize while maintaining overall consistency through the shared layout data structure.
Solution Approach 2:
The layout and pagination calculations are performed once and then copied to multiple renderers that need them. Each renderer receives the same layout data structure without recalculating, ensuring consistency across different output formats while allowing each renderer to maintain its own format-specific processing capabilities.
2Adaptability or versatility
If each renderer recalculates layout/pagination for each format, then format-specific optimization is achieved, but computational load increases
Solution Approach 1:
The layout and pagination calculations are performed in advance by the report processing module before the actual rendering occurs. This preliminary calculation eliminates the need for each renderer to recalculate these parameters, significantly reducing redundant computational operations while allowing renderers to focus only on format-specific transformations.
3Adaptability or versatility
If multiple renderers are used for different formats, then format-specific rendering capabilities are improved, but system complexity increases
Solution Approach 1:
The report processing module serves as a universal component that performs layout and pagination calculations that are applicable to all renderers regardless of output format. This multi-functional approach allows a single component to support multiple renderers, reducing overall system complexity while maintaining format-specific rendering capabilities through the modular renderer architecture.
4Reliability
If redundant handshaking and controls are passed between applications, then communication compatibility is ensured, but network communication efficiency deteriorates
Solution Approach 1:
The system extracts and eliminates redundant handshaking and control messages from the communication protocol between the report processing module and renderers. By removing these unnecessary communication overheads while retaining essential coordination signals, the system maintains compatibility and reliability without the penalty of excessive network traffic.
Data Source
AI summary
A computer output display system is provided. The system includes a layout component to determine one or more rendering rules that are applicable to a subset of display output controls. A format component communicates the rendering rules via a generic protocol that is employed by the subset of display output controls to render a display.