Replies: 1 comment 1 reply
-
I have not yet used either variant; my use cases so far are still quite limited. I guess looking at the names only, I would assume ColumnBox to be a bit like the 2-div layout in newspapers or 3-div layouts, e. g. side by side? My own long term goal is to be able to render all my autogenerated HTML pages (I use ruby to autogenerate the code actually) as .pdf files eventually seamlessly. There are work arounds for this, e. g. headless rendering and stuff like that, but I'd kind of love to be able to do the "write once, generate everything", so being able to offer .pdf for all my webpage content one day would be great, without having to spend too much time styling any of that (I already do the styling on the webpage, so it would be nice if .pdf could take some of that. Does not have to be perfect, just the basic stuff, colours, borders, spacing, margin ... that's it.) |
Beta Was this translation helpful? Give feedback.
-
Hi!
There will be some fairly major changes in
HexaPDF::Composer
and the wholeHexaPDF::Layout
module in the upcoming release. Among others, there is a newColumnBox
class for laying out content in columns.Additionally, I want to make it easier to use the classes from the
HexaPDF::Layout
module without usingHexaPDF::Composer
.Therefore I would like to ask if there are pain points when using those layout classes and if so, what are the pain points?
Beta Was this translation helpful? Give feedback.
All reactions