Sorry, it's still an API I'm trying to decide upon and figure out, simple
as it is... largely, I just want that someone who used
..::Filter::EdgeSimplify has immediate access to all the other powers of
GD::Image as well...
problem is, something like ...
my $file = GD::Image::Filter::EdgeSimplify->newFromPng('blahblah');
$file->simplify;
... seems awkward to me, now that I've typed it out. Trying to do this, as
I think about it, may be unnecessary.
use GD::Image;
use GD::Image::Filter::EdgeSimplify;
my $pic = GD::Image->newFromPng('blahblah');
GD::Image::Filter::EdgeSimplify->render($pic); #assuming a ref
that seems awkward, too...
Perhaps I should do what's already being done w/Image::Filters (I discussed
this very briefly with the creator of those wrapped-c filters, who no
longer maintains that namespace, by the way) with something more like:
use GD::Image::Filter;
my $pic = GD::Image::Filter->newFromPng('blahblah'); # extended?
$pic->filter('EdgeSimplify'); # maps out to GD::Image::Filter::EdgeSimplify
on demand, but offers a unified api for future pure perl filters
*thinks*
On Sat, Jul 13, 2013 at 11:48 PM, Aristotle Pagaltzis <pagalt...@gmx.de>wrote:
> Hi Joshua,
>
> * Joshua Turcotte <joshua.eric.turco...@gmail.com> [2013-07-13 21:20]:
> > […] image edge simplification algorithm […]
> >
> > To that end, one shot in the dark could be ..::Filter::Simple or
> > Filter::SimpleEdge or something to that end.
>
> sounds to me like you want GD::Image::Filter::EdgeSimplify.
>
> > I'm refactoring the algorithm currently to operate as a module rather
> > than a script, and I'd like, if someone doth use
> > GD::Image::Filter::WoopWoop; that they'd get the extended capabilities
> > of GD::Image right along with it (rather than having to make the two
> > play nice with each other themselves.)
>
> I don’t follow. Do you mean they should get a GD::Image that has methods
> for both algorithms, or something along these lines?
>
> Regards,
> --
> Aristotle Pagaltzis // <http://plasmasturm.org/>
>
--
~jet
