"I was thinking that writing a file out to disc and then reading it back in was a messy workaround ..."

I agree and had the same thought myself. There is a way to do this with in-memory filehandles; however, there were two reasons why I didn't pursue this.

  1. I didn't know if you'd want to reuse the generated image. I see from your "new, additional information" this isn't the case; or, at least, I assume it's not.

    By the way, the "unlink $png_file;" was intended as optional for you and as housekeeping for me; I omitted to specifically state that.

  2. I recalled that you were stuck with a fairly old version of Perl from your ISP. See the "Technical note" in "Opening a filehandle into an in-memory scalar" which may possibly still be a "hurdle" for you.

As well as a filename, and a GD::Image object when that bug gets fixed, PDF::API2::image() can also take a filehandle. The following code produces exactly the same PDF as my previous code. 

#!/usr/bin/env perl

use strict;
use warnings;
use autodie;

use PDF::API2;
use GD::Tiler 'tile';

my $pdf_file = 'tiled_dogs.pdf';
my @dog_jpegs = qw{husky.jpg labrador.jpg retriever.jpg};

my $tiled_dogs = tile(
    Images => [@dog_jpegs],
    Center          => 1,
    ImagesPerRow    => 3,
);

my $pdf = PDF::API2::->new();
my $page = $pdf->page();

open my $png_fh, '<:raw', \$tiled_dogs;
my $canine_triptych = $pdf->image($png_fh);
close $png_fh;

$page->object($canine_triptych, 100, 650, 400);
$pdf->save($pdf_file);

[download]

Assuming you don't want to keep the generated image, and you're not confronted with technical difficulties, this would be a better solution. I would expect this would also be much faster; but do Benchmark if speed is important to you.

Update: Two minor tweaks to the code: removed parts left over from the previous script that were no longer needed here.

— Ken

In reply to Re^3: Image modules not returning or accepting GD::Image by kcott
in thread Image modules not returning or accepting GD::Image by Bod

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.