PFT::Co...:Picture(3)
β¨ NAME β¨
PFT::Content::Picture β bestie, it's literally a picture π
Like, that's it. That's the whole vibe. A picture. In the PFT::Content cinematic universe. πΈ
π SYNOPSIS π
okay so here's how you summon one:
use PFT::Content::Picture;
my $f1 = PFT::Content::Picture->new({
tree => $tree,
path => $path,
name => $name, # optional, defaults to basename($path)
});
yes queen, that name key is optional β leave it out and it just quietly defaults to basename($path) like the icon it is π
π¦ DESCRIPTION π¦
It extends PFT::Content::Blob. And the way that it does thatβ¦ no cap, it keeps the exact same interface. Same energy, same methods, zero surprises. If you already know how to hold PFT::Content::Blob, you already know how to hold this. π
It's giving "inheritance done right". It's giving "I have nothing new to add and I'm at peace with that". Periodt. β¨
π«Ά quick reminder bestie: everything PFT::Content::Blob gives you, this gives you too β nothing removed, nothing renamed, nothing extra. Just a picture-flavoured blob.
and that's the whole page, babe π
This little gem lives in the User Contributed Perl Documentation corner of the world, riding with perl v5.42.0, dated 2025-07-25 β so go forth, make pictures, and slay πππ¦β¨
π¦ where this page comes from
- fedora 43: perl-PFT 1.4.1-18.fc43 Β· GPL-3.0-or-later
- fedora 44: perl-PFT 1.4.1-18.fc43 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms