4 ms·
Frankly, we were not able to find something suitable. It needed to be fast (our largest report has like 2000 pages), needed to support advanced layouting (image
by cygned 9y ago
Frankly, we were not able to find something suitable. It needed to be fast (our largest report has like 2000 pages), needed to support advanced layouting (images outside of usual print margins, multi-pages tables with continued headers, ...) and we wanted to have some kind of templating language. Native node.js would have been nice, but not required.
Maybe I was out of luck, butI couldn't find anything useful fulfilling these requirements - if you have suggestions, I'd be interested in seeing what's possible.
How it went, though? Due to our use cases, this LaTeX service is a complexity beast. The templating isn't fun; LaTeX was not created to be templated itself. We have escaping in place, but from time to time user input breaks it. We have no way to let users create their own reports at this point. There are multiple reasons, but LaTeX being not that beginner-friendly is definitely one of them.
But given the template is correct and the user input is sane, it's fast and simply works.
- flukus 9y agoThe "least worst" I've ever used to SSRS (Microsoft), not sure if the 2000 pages will cause an issue or if the images outside the borders are possible though. Apparently it supports other data sources but I'm not sure how well, I've got an upcoming task at work to investigate this. But 2000 pages? That's a data dump, not a report.
- cygned 9y agoThose reports are usually printed and sent to members. Therefore, even the 2000 pages report needs to be well-formatted and layouted correctly, including addresses, brand images and stuff. Amount wise it really feels like a dump, yes.