There goes my unique flask-extension documentation style. :(
Image manipulation library for PHP 5.3
11–20 of 29 posts
Re: Image manipulation library for PHP 5.3
#12There goes my unique flask-extension documentation style. :(
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.
Re: Image manipulation library for PHP 5.3
#13Looks very nice, a worthy successor to http://wideimage.sourceforge.net/
I look forward to using it.
Re: Image manipulation library for PHP 5.3
#14Just 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/
Re: Image manipulation library for PHP 5.3
#15Looks great, but...I clicked on "examples" and expected examples of output in addition to code examples...Please add these if you have time.
thanks, will do!
Re: Image manipulation library for PHP 5.3
#16Just 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
Re: Image manipulation library for PHP 5.3
#17Whats\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 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.
Re: Image manipulation library for PHP 5.3
#18Whats\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…
> the backslash is ugly
Not only that, it's very unconfortable to type in some international keyboard layouts.
Re: Image manipulation library for PHP 5.3
#19Re: Image manipulation library for PHP 5.3
#20Whats\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…
They are harder (than many other commonly used characters) to distinguish from regular text as well.