Re: PHPTAL package name
| From: | till | Date: | Thu, 26 Nov 2009 18:23:56 +0000 |
| Subject: | Re: PHPTAL package name | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-53065@lists.php.net to get a copy of this message | ||
Hey Kornel,
you are correct, changing the packagre name requires changing the
class names and possibly the file structure in your VCS
(HTML/Template/PHPTAL.php, etc.).
I don't know about the upgrade procedure for your existing users, but
my guess is that if they use a pear-install already, the "new" package
name would hint at a totally new package for the user. E.g. if they
did pear install PHPTAL before, they now need to do pear install
HTML_Template_PHPTAL.
Let me know if this answers your question.
Till
On Thu, Nov 26, 2009 at 5:41 PM, Kornel Lesinski
<kornel@aardvarkmedia.co.uk> wrote:
> Hello, any advice on this?
>
> On 10 Nov 2009, at 23:41, Kornel Lesiński wrote:
>
>> I've been informed on #pear that PHPTAL package should be renamed to
>> HTML_Template_PHPTAL. That category definitely suits the project, but as far
>> as I'm aware, this also requires change of package name and class names.
>>
>> Just change of package name doesn't sound very bad, it'll only require
>> existing pear users to uninstall old package first (right?), but change of
>> class name prefix seems very disruptive to me. It would require changes not
>> only all over PHPTAL codebase, but also in all existing PHPTAL-based
>> projects/framework adapters and some 3rd party extensions.
>>
>> I could provide wrappers or dummy classes that inherit new ones under old
>> names, but that would be messy and nearly double number of files that have
>> to be loaded (startup performance is PHPTAL's weak point already, and I
>> don't want PHPTAL to be perceived as bloated and high overhead).
>>
>> Also, without real namespaces class names that are already overly long
>> (e.g. PHPTAL_Php_Attribute_TAL_Condition) would get even longer. Some of
>> those classes are visible to users.
>>
>>
>> I wouldn't mind renaming classes when migrating to PEAR2. With real
>> namespaces these problems are minuscule.
>>
>>
>> So my questions are:
>>
>> Is it possible to have "PHPTAL" package in HTML/Template category? or
>> HTML_Template_PHPTAL package that uses only PHPTAL as class name prefix?
>> Can renaming be deferred until PEAR2?
>
> --
> regards, Kornel
>
>
> --
> PEAR Development Mailing List (http://pear.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>