Re: TESTERS ONLY: new-gopear.php is available in cvs
| From: | Arnaud Limbourg | Date: | Mon, 04 Apr 2005 15:20:21 +0000 |
| Subject: | Re: TESTERS ONLY: new-gopear.php is available in cvs | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-37074@lists.php.net to get a copy of this message | ||
Hi,
I just ran the new gopear under OS X 10.3.8 (Panther).
In cli mode it works well.
In web mode when an error occurs the page has a weird layout. I'll send
you the screenshot via another mail.
When no error occurs things proceed smoothly. There might be a refresh
problem from ProgressBar though, under safari it makesone big jump to
70% then nothing until a 100% is reached.
Now onto fixing my install since I forgot to to pear -c newconf it
overrode my conf :)
Good job Greg, now windows will likely be the problem, there are a few
issues lurking with windows iirc.
Arnaud.
Greg Beaver wrote:
> Hi,
>
> as a followup to my initial announcement, I have committed the work I'm
> doing to pearweb/public_html/new-gopear.php.
>
> ***DO NOT USE THIS IN PRODUCTION***
>
> OK, disclaimers aside, here is what I have done so far:
>
> 1) moved almost everything into functions
> 2) tested CLI install on windows
>
> Here is what I have *not* done - so please don't try any of these things
> out until I get a chance to test and bugfix, or you might screw things up.
>
> 1) tested Web install on windows
> 2) tested CLI install on unix
> 3) tested Web install on unix
>
> I also have not done any regression testing, just stepping through with
> a debugger to verify that all pre-existing global variables are
> correctly initialized.
>
> The next steps are
>
> 1) test Web windows/all unix
> 2) take all global declarations out of functions and instead use parameters
> 3) analyze the code to locate commonality
> 4) refactor just enough to allow easy unit-testing
> 5) write unit tests
> 6) refactor global variables into class variables both for better
> documentation and code re-use (not for traditional OO reasons of
> multiple object use)
> 7) implement Web, CLI and Common classes for different installation types
>
> Once I get to #5, I will need help. I would prefer to see folks working
> on tests even as the refactoring begins, so this doesn't take forever
> and a day.
>
> Greg
>