Re: [pear-webmaster] Object oriented design for the backend
| From: | Pierre-Alain Joye | Date: | Fri, 18 Jun 2004 17:24:40 +0000 |
| Subject: | Re: [pear-webmaster] Object oriented design for the backend | ||
| References: | 1 2 3 | Groups: | php.pear.webmaster |
| Request: | Send a blank email to pear-webmaster+get-2597@lists.php.net to get a copy of this message | ||
On Fri, 18 Jun 2004 08:07:03 +0200
mj@php.net (Martin Jansen) wrote:
> We'll see. Using 4.1 is absolutely no hard requirement in my
> book.
Neither in mine. Even not MySql itself :)
> > internal classes. Maybe it's a good idea to have all common
> > classes in a basic version inside the installer and a derived
> > version for the web stuff, so that we can saftly modify things,
> > without damaging the installer?
> I have been thinking about this as well, but I haven't come up
> with a good solution yet.
The good solution is to move the installer out of the pearweb tree.
And then yes, use/extends/override it.
> > In general, I think, when we start reworking the backend, we can
> > more or less do a complete refactoring, introducing templates
> > and stuff.
>
> I would like to first concentrate solely on the backend. Revising
> the frontend should be a separate step.
Fully agreed. Doing that also move the frontend out of the backend
(sounds obvious but not really the case right now :) ).
The model sounds good here, some pedantics thingies but after a
quick review and compares, everything is covered.
About the DB, I do not feel good to be MySql dependent. I'm more to
be DB independent.
--Pierre