Re: Re: cvs: pear /Selenium ChangeLog Selenium.php TODO makepackage.php /Selenium/Selenium Exception.php

Well, prior to the PEAR_ prefix thing, AFAIK the was an unwritten rule that all classes had to have at least one '_underscore_' in to fix the issue of clashing with PHP Core Classes (which yet another unwritten rule says they are not going to use '_underscores_' in the names.) ** this kind of needs RFQ'ing up!.... -- Wow - 2004 was only last week ;) http://64.233.161.104/search?q=cache:g-9Murl3pn8J:www.pear.php.net/pepr/pepr-proposal-show.php%3Fid%3D55 I'd rather we flagged proposals as deleted, than make them dissapear.... PHPUnit(2) was created when we didnt realize this issue would exist, and hadn't thought of any cures. Regards Alan Shin OHNO wrote:

Hi, Alan. I'm author of this package. I had always trouble deciding the prefix of this package. When I got my CVS account, I asked my account opener, Pierre what to do with this package. Following is the what we talk about: I wrote:

As for the name of the Selenium Package, IMHO, I like Testing prefix, but as long as PHPUnit and PHPUnit2 do not have the prefix, I think having Testing prefix is not a good choice. What do you think?

Pierre wrote:

The category in pearweb is one thing, the name of your package another. I think you should go with "Selenium".

At that time, I thought all PEAR packages are going to have PEAR_ prefix, and I didn't know what to with this name. If there are any problems, I'm open for the discussion. Also I like to know the PEAR way. Thanks, Shin On 10/14/06, Alan Knowles <alan@akbkhome.com> wrote:

I must of missed this one - but should it not be called Testing_Selenium ? Regards Alan Shin OHNO wrote:

shin          Thu Oct 12 17:11:29 2006 UTC

Modified files:

    /pear/Selenium    ChangeLog Selenium.php TODO makepackage.php
    /pear/Selenium/Selenium   Exception.php

Log: For the version 0.1.5 Added TODO.