Image manipulation library for PHP 5.3

http://imagine.readthedocs.org

by avalanche123 • 15 years ago

83 28 15 years ago

imagine.readthedocs.org

sunsu• 15 years ago

Besides being a great library, its an excellent example of well written PHP code.

johnny22• 15 years ago

i am so glad to be reminded of this. Now i just need to implement a filter for assetic at some point.

Assetic still relies on opti{png,jpeg} which i'm sure works pretty well, but also requires one to call out to an external program.

snorkel2• 15 years ago

Whats\With\All\The\Backslashes? Am I only one seeing that in the examples?

bobthecow• 15 years ago

Welcome to PHP 5.3 :)

chrisrickard• 15 years ago

I wonder how many times I will need to see PHP 5.3's backslashes before they look 'correct' :)

zerosanity• 15 years ago

Since this is a PHP 5.3 library it's using PHP namespaces.

FuzzyDunlop2• 15 years ago

It's PHP 5.3's namespacing functionality, in a nutshell.

Symfony2 and Lithium are two frameworks I can currently think of that use them extensively. On the one hand, Symfony2 has a quite extreme implementation, and on the other, Lithium's is much more concise. The backslashes can be used to represent a hierarchy.

robmorgan• 15 years ago

Zend Framework 2.0 is also a big user of PHP namespaces. It's in beta the moment.

snorkel2• 15 years ago

Oh for the love of science, please let this be a bad dream ... is the parent object referred to as C:\ by any chance?

iisbum• 15 years ago

PHP's method for using Namespaces: http://php.net/manual/en/language.namespaces.php

mzarate06• 15 years ago

Namespaces, as others have mentioned. The first question I had when I first encountered that as the Namespace operator was: "Why not the double colon operator?"

Double colon is already being used for static member referencing, and in a few talks I've heard from Rasmus, they weren't able to find a way to overload it for Namespaces.

Another option that was discussed was a triple colon operator, which most were opposed to b/c of it's length. I personally think the backslash is ugly, and I kind of like the triple colon operator better b/c of it's similarity to the double colon operator. Regardless of which one is prettier, I wish the double colon operator could have been overloaded.

1880• 15 years ago

> the backslash is ugly

Not only that, it's very unconfortable to type in some international keyboard layouts.

gurraman• 15 years ago

They are harder (than many other commonly used characters) to distinguish from regular text as well.

notJim• 15 years ago

IIRC, the reasoning against double colons was that if you had a class and a namespace with the same name, it's impossible to tell whether SomeThing::Do() is calling a function in the SomeThing namespace, or the static Do function on the SomeThing class. One could argue that they could simple not allow namespaces and classes to share names, but I guess they didn't like that idea, either.

I hope I'm stating this right, I must admit it's from a fuzzy recollection.

brador• 15 years ago

Looks great, but...I clicked on "examples" and expected examples of output in addition to code examples...Please add these if you have time.

avalanche1233• 15 years ago

thanks, will do!

FuzzyDunlop2• 15 years ago

This has appeared at just the right time, now I'm re-working my project's image manipulation classes. The PHP GD library functions are a nightmare for readability.

I'll be having a little play about with what I intend to implement and if it works out well I'll likely implement it in my project proper!

> “Why didn’t he keep width and height as simple integer parameters in every method that needed those?” or “Why is x and y coordinates are an object called Point?”

Seems to me that PHP needs to turn its own primitives into objects so they can be type hinted. Trying to figure out which of a dozen number validation functions to use is an utter clusterfuck at the best of times.

the_mitsuhiko• 15 years ago

There goes my unique flask-extension documentation style. :(

avalanche1233• 15 years ago

sorry, it looked so awesome and I noticed the kind requirement to use it for flask-only projects after rolled the new sphinx design out. I promise to use a different theme and is something I'm working on now.

bingaling• 15 years ago

Looks very nice, a worthy successor to http://wideimage.sourceforge.net/

I look forward to using it.

ipsin3• 15 years ago

Just curious, is there a reason you chose GD over imlib2?

I've used both and I think I prefer imlib2 for flexibility and breadth, and there's already at least one imlib2 binding for PHP: http://pp.siedziba.pl/

avalanche1233• 15 years ago

very cool, I'll see about adding support for it too

ipsin3• 15 years ago

Probably not worth the trouble, since as mp3geek points out, it's stale (according to wikipedia, a deprecated/defunct part of Enlightenment)

mp3geek• 15 years ago

Hasn't been updated in a while? Is it even still supported?

ipsin3• 15 years ago

Thanks, I'd seen so many language bindings for imlib2 (and, yes, gd) that I'd assumed it was an active project, but you're right that it's not. Also gd does a lot more than it used to.

Thanks for the correction!

chrismsnz• 15 years ago

It's really good to see some well engineered PHP software coming out.

For my projects I've moved out to Python after having dealt with legacy trash like Wordpress, Google's api libraries, over-engineered frameworks like ZF and lets just say the less said about Propel the better.

Code like this, Symfony 2, Doctrine 2, Lithium etc... are a breath of fresh air. Their obviously written by a group of talented devs and after cutting ties with legacy PHP versions < 5.3 the future of "modern" PHP is looking bright!

Image manipulation library for PHP 5.3

Related Stories