i have pet chickens, i make drawings, and i write software of questionable usefulness. that's pretty much the extent of my personality. ask me about array programming, decker, or anything, really.


Decker 1.44 offers a (subjectively) delightful assortment of additions and enhancements, including:

  • The app.render[] function for taking "screenshots" of cards or widgets.
  • Vastly improved performance for Lil's @ operator in some situations.
  • Support for writing variadic functions in Lil.

And of course, the thrilling release version of the pdf module, which among other things opens up options for allowing Decker e-zines to offer a "printable" version of themselves under scripted control.

Try it out on your home computer today, and don't forget that Decker Fantasy Camp 2024 is right around the corner!


You must log in to comment.

in reply to @internet-janitor's post:

Hi, I was just trying out the pdf module in the new version and (at least the Windows build in Windows 10) it seems to be producing slightly wonky PDFs, they'll view fine in Firefox but Adobe Reader is giving me a bunch of blank pages and an error message. I am guessing there's something slightly off in the formatting that Firefox can handle but Adobe Reader objects to?

Thinking more broadly in terms of the suggestion about printable e-zines, I'm figuring that if there's a scrolling text field just rendering out the card as an image would only get the visible bit of the text field. Is there any way of rendering out the contents of a text field as one big long image?

I'll investigate Adobe Reader compatibility; In my testing the current outputs seem to work correctly in Preview.app, Firefox, and Chrome.

Scrolling text (and many other interactive elements) would certainly require some special-casing for printable results. If you want to render text as a very long image you'd use the same approach you would in an interactive script: canvas.textsize[] can measure the dimensions of rich or plain text wrapped within a specified width, and canvas.text[] can draw wrapped rich or plain text in a manner similar to a field widget.

I was able to identify and correct a few minor problems in PDF output with pdfinfo, and those patches are checked into the git repo as v1.1 of the pdf module. It's still unclear why Acrobat doesn't like inline image streams. If anyone is aware of general-purpose PDF validation tools I should experiment with, drop me a line.