12-06-2024 01:56 PM
@Hooovahh wrote:
So he went into photoshop, scaled the image and resubmitted. This time they accepted it, and he was eventually published.
I could have done it directly in LabVIEW by e.g. just turning every pixels into a 8x8 pixel area of the same color. for 64 times more pixels.
(It actually might not really have been "policy", but a limitation of the typesetting system they use).
(I still remember when the professor complained about the size of his PowerPoint files until I noticed that he had slides with dozens of stamp sized pictures, each actually a resized multi-megapixel image. 😄 )
12-12-2024 06:29 AM
wiebe@CARYA wrote:Of course I suggest to switch to vector based graphs (I've been creating PDFs for 25 years 😎)...
But now I have to make clear that vector based graphs might dramatically increase or decrease the PDF size, depending on the data...
That long?! 🙂
A few years back I was frustrated with low quality calibration plots in certificates, and did a bit of a look round at my options. I had a few issues with the Gnuplot SVG terminal (can't remember what; I've been an on/off Gnuplot user for the last twenty years, as well as matplotlib) and ended up creating my own SVG generation library in LV. It was relatively quick and painless, and did double duty as a means of producing SVG QR codes at the same time.
Sorry to say, PDF generation was done without the Carya toolkit - we already had a different system for use with C#, so I wrote a wrapper for LV - but it was a reminder of just how painful of how reporting can be without the right tools!
12-12-2024 09:20 AM
@thoult wrote:
Sorry to say, PDF generation was done without the Carya toolkit - we already had a different system for use with C#, so I wrote a wrapper for LV - but it was a reminder of just how painful of how reporting can be without the right tools!
No worries, it's free now. If I have a few weeks time, I'll open source it. Just remember that iTextSharp is only free for open source projects. Not even when it's used in a free LV toolkit.
@thoult wrote:That long?! 🙂
The first release of the PDF Toolkit was written in LV6, in 2006 IIRC. I'm sure I had rudimentary (insert a jpg on a page) PDF creation way before that. So [22, 25) years.
Drawing a graph isn't hard, it's just lines, dots and text...
Making a universal API is very hard though. It got easier with OO though.