Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Image manipulation library for PHP 5.3

imagine.readthedocs.org

Post reply on HN
Print view View original

21–29 of 29 posts

Re: Image manipulation library for PHP 5.3

#21

Post by minikomi »

1880 wrote: post #18
mzarate06 wrote: post #17

Earlier quoted context omitted.

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…

> the backslash is ugly Not only that, it's very unconfortable to type in some international keyboard layouts.

Agreed. Although function-¥ does give my hands a stretch now and then, I don't want to be typing it constantly..

Re: Image manipulation library for PHP 5.3

#22

Post by mp3geek »

ipsin wrote: post #14

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/

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

Re: Image manipulation library for PHP 5.3

#23

Post by ipsin »

mp3geek wrote: post #22
ipsin wrote: post #14

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/

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

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!

Re: Image manipulation library for PHP 5.3

#24

Post by ipsin »

avalanche123 wrote: post #16
ipsin wrote: post #14

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/

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

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

Re: Image manipulation library for PHP 5.3

#25

Post by notJim »

mzarate06 wrote: post #17
snorkel wrote: post #4

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

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…

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.

Re: Image manipulation library for PHP 5.3

#26

Post by robmorgan »

FuzzyDunlop wrote: post #8
snorkel wrote: post #4

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

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.

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

Re: Image manipulation library for PHP 5.3

#27

Post by chrismsnz »

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!

Re: Image manipulation library for PHP 5.3

#28

Post by tripzilch »

1880 wrote: post #18
mzarate06 wrote: post #17

Earlier quoted context omitted.

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…

> the backslash is ugly Not only that, it's very unconfortable to type in some international keyboard layouts.

If you're talking about the German layout and AltGr, then so are the []{} keys, which are already used quite a lot in PHP programming.

It's the main reason why, even though my phyiscal keys are in German layout, I still have the USA layout in software. It's just nice to be able to make [] with a single key press :)

Re: Image manipulation library for PHP 5.3

#29

Post by snorkel »

FuzzyDunlop wrote: post #8
snorkel wrote: post #4

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

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.

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