nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Need something like a "Vertical Tab" to position text at the bottom of the last page (PDF)

hvb

[font="cambria;"]Use Case[/font][font="cambria;"][font="calibri;"]I have an invoice report with several pages. Some dynamic text items should be displayed near the bottom of the last page.[/font][/font][font="cambria;"] [/font][font="cambria;"][font="calibri;"][font="cambria;"]Obviously no solution available[/font][/font][/font][font="cambria;"][font="calibri;"]I am aware that for simple reports with fixed row height in a table, it is possible to count the rows, estimate the space used by the table, and add another table with just enough rows between the invoice positions table and the dynamic text. However, this only works if the row height is fixed and if I know where the table starts on the page.[/font][/font][font="cambria;"][font="calibri;"]Unfortunately, this is not the case in my reports, as their is dynamic text (several lines) before the table and the descriptive text in the rows may wrap.[/font][/font][font="cambria;"] [/font][font="cambria;"][font="calibri;"]There is a very old known bug that this does not work with BIRT.[/font][/font][font="cambria;"] [/font][font="cambria;"][font="calibri;"]One idea that came to my mind was to use the Footer of the MasterPage.[/font][/font][font="cambria;"][font="calibri;"]However, it is only possible to hide the footer on the last page, but not to show it only on the last page.[/font][/font][font="cambria;"][font="calibri;"]Even if that worked, it had negative impact because the space for the footer would have been wasted on all pages except the last one.[/font][/font][font="cambria;"][font="calibri;"]BTW it would be great if the visibility condition could be extended for every item inside the MasterPage for three different cases: first page, "inbetween" page, last page.[/font][/font][font="cambria;"][font="calibri;"]And another great feature would be if the space for a non-displayed header or footer item (which is wasted at the moment) could be "returned" to the content (for the footer, items above the hidden items should "drop" down instead of the following items to go up).[/font][/font][font="cambria;"] [/font][font="cambria;"][font="calibri;"][font="calibri;"][font="cambria;"]Idea for "VerticalTab" item[/font][/font][/font][/font][font="calibri;"]Having some experience with other tools like ReportLab, I wonder if its possible to create an Extended Item I call VerticalTab that works as follows (with ReportLab, that would be a snap...):[/font]<ul class='bbc'><li>[font="calibri;"]It has only an effect when using FixedLayout mode (e.g. multi-page PDF).[/font]</li><li>[font="calibri;"]There is only one property:[font="calibri;"] distanceToPageBottom. This property specified the distance to the bottom of the page (ignoring the page footer height and the page bottom margin, but that's not really important).[/font][/font]</li><li>[font="calibri;"]The effect is as follows: When the Layout Engine executes this item, the item (or the layout engine) looks at the current y position and computes how many space is still available below. It then compares this value (let's call it currentDTB) to the specified distanceToPageBottom:[/font]</li><li>[font="calibri;"]currentDPB > distanceToPageBottom: Set y position = distanceToPageBottom[/font]</li><li>[font="calibri;"]currentDPB = distanceToPageBottom: nichts tun[/font]</li><li>[font="calibri;"]currentDPB < distanceToPageBottom: force a page break[/font]</li></ul>
[font="calibri;"]In other words, assure that the next item will start exactly at the specified distanceToPageBottom. [/font][font="calibri;"]The last case is special: If there's not enough space left on the current page, force a page break and render the VerticalTab again there - such that the next item stands alone at the bottom of the last page...[/font] [font="calibri;"]This would be easy to do if the item could see the current y position during its size computation.[/font][font="calibri;"]In Reportlab, this is the case (there, the central method "wrap" has availH and availW arguments).[/font] [font="calibri;"]It might also work if the item could tell it has a height 0 when it is created, but during the actual rendering process it would increase the current y position as needed.[/font] [font="calibri;"]After studying the BIRT code and the RotatedText plugin, I have to admit that I just don't undestand how the layout engine is actually working. It seems quite complex.[/font] [font="calibri;"]I didn't find any other Extended Item example except those in the BIRT controls lib, which are all bitmap-image-based.[/font][font="calibri;"]My gut feeling tells me that the following source files are important here:[/font][font="calibri;"][font="calibri, sans-serif;"]orgeclipsebirtreportenginelayoutemitterPageDeviceRender.java, method [/font][/font][font="calibri;"][font="calibri, sans-serif;"]getActualPageBodyHeight[/font][/font][font="calibri;"]Package [font="calibri, sans-serif;"]org.eclipse.birt.report.enginesrcorgeclipsebirtreportenginenLayoutareaimpl, with the classes AbstractArea, ContainerArea, PageArea and so on.[/font][/font] [font="calibri;"][font="calibri, sans-serif;"]But I just dont know how to start. [/font][/font][font="calibri;"][font="calibri, sans-serif;"]Any hints or pointers?[/font][/font]

Find more posts tagged with

Comments

There are no comments yet