Multi-Page Table Rendering via Height-Based Row Partitioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data storage systems management applications, such as Microsoft PowerPoint, lack support for table pagination across multiple slides, leading to content overflow when a data set spans more than a single page, as libraries like Apache POI do not provide APIs for rendering tables across multiple pages.
Innovation Solution
A method for processing and rendering data sets by partitioning them into pages, where the first page includes a header section and subsequent pages do not, using calculations to determine the number of rows based on available height, allowing for efficient pagination across multiple pages in a specified file format like Microsoft PowerPoint.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If table data is rendered on a single page, then the layout is simple and complete, but content overflow occurs when the data set spans more than one page
Solution Approach 1:
The patent divides the table rendering process into multiple pages by calculating the available height on each page and partitioning the data set accordingly. The first page includes header, footer, and margin sections, while subsequent pages contain only data rows. This segmentation allows the complete data set to be displayed across multiple pages without overflow, resolving the contradiction between layout completeness and page capacity.
2Ease of manufacture
If libraries like Apache POI are used for rendering, then the implementation is straightforward, but pagination across multiple pages is not supported
Solution Approach 1:
The patent performs preliminary calculations of page dimensions, header/footer heights, and margin requirements before rendering the table. By pre-determining the number of rows that fit on each page based on available height calculations, the system enables pagination functionality without requiring complex runtime adjustments, thus maintaining implementation simplicity while adding multi-page capability.
3Ease of operation
If the header section is included on every page, then navigation is easier, but the available space for data rows decreases
Solution Approach 1:
The patent applies local quality by including the header and footer sections only on the first page of the table, while subsequent pages contain only the data rows. This approach optimizes the distribution of page elements based on their functional requirements: the header provides navigation context where most needed (first page), while data rows require maximum space on following pages. This resolves the contradiction by making the layout adaptive rather than uniform across all pages.
Data Source
AI summary
Techniques for processing a data set include: partitioning the data set into portions each including rows of data of the data set, a different one of the portions is included in a different one of a pages of a table, and rendering the pages of the table. A first number of rows of the data set is determined for a first page. The first number of rows is determined in accordance with a first plurality of heights including a height of a header section, a height of a footer section, heights of a plurality of margins, a total height of each page of the table, and a height of each row of the table. A second number of rows is determined for a second page. The second number of rows is determined in accordance with a second plurality of heights including at least some of the first plurality of heights.