Deprecating GD functions imagettftext/bbox
| From: | Lonny Kapelushnik | Date: | Tue, 22 Jul 2014 19:01:49 +0000 |
| Subject: | Deprecating GD functions imagettftext/bbox | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-75880@lists.php.net to get a copy of this message | ||
Morning,
I propose deprecating two GD functions: imagettftext and imagettfbbox.
The reasons I would like to deprecate them are:
1. Their functionality is a subset of imagefttext and imageftbbox
2. The imagettf* functions have the same requirements as the imageft* functions
3. The imagettf* functions parameters are compatible with the imageft* functions parameters
As far as I can tell the original reason for having both functions was because PHP LIBGD is a custom
implementation of LIBGD that had additional functionality from the actual LIBGD. While this is still
the case it seems that now the required functions (gdImageStringFT and gdImageStringFTEx) exist in
both libraries.
The only difference between imagettf* and imageft* functions is the imagettf* functions do not
provide the optional ‘extrainfo’ parameter
The only step to migrate from the imagettf* functions to imageft* functions is to change the
function names from ‘imagettf*’ to ‘imageft*'
I would like to create a timeline to deprecate and remove the imagettf* functions. Providing a
timeline will allow for:
1. Clarity for which PHP functions to use going forward
2. Ability to plan a migration to the new PHP functions
3. Clarity for which PHP functions to improve in php-src
4. Ability to clean up some of the GD code in php-src
I will hold off on proposing an actual timeline for now.
I can implement any coding changes needed.
Please let me know the general thoughts to deprecating these functions. If the reception is positive
I would like to create an RFC to discuss this in full and come up with a timeline.
–––
Hakuna Matata!
Lonny Kapelushnik
https://www.lonnylot.com
732.685.9175