Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75880
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain lonnylot.com designates 209.85.192.44 as permitted sender)
Content-Type: multipart/alternative; boundary="Apple-Mail=_6F2216F9-A7E5-4A96-A3E9-DA8C18BDE6CB"
Date: Tue, 22 Jul 2014 15:01:49 -0400
Message-ID: <F87DEB6A-3F42-4903-9D93-3CF4126897AB@lonnylot.com>
Cc: pierre.php@gmail.com
To: internals@lists.php.net
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Deprecating GD functions imagettftext/bbox
From: lonny@lonnylot.com (Lonny Kapelushnik)

--Apple-Mail=_6F2216F9-A7E5-4A96-A3E9-DA8C18BDE6CB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

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 =91extrainfo=92 =
parameter

The only step to migrate from the imagettf* functions to imageft* =
functions is to change the function names from =91imagettf*=92 to =
=91imageft*'

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.

=96=96=96
Hakuna Matata!
Lonny Kapelushnik
https://www.lonnylot.com
732.685.9175


--Apple-Mail=_6F2216F9-A7E5-4A96-A3E9-DA8C18BDE6CB--