Re: Framework Development (2)

Hello Sebastiao, Monday, June 17, 2002, 2:23:17 PM, you wrote: >> "Stig S. Bakken" <ssb@fast.no> wrote*: >> >> On Sun, 2002-06-16 at 22:47, Martin Jansen wrote: >>> On Sun, 16 Jun 2002 16:57:47 -0300 (BRT), Sebastiao Rocha wrote: On >>> Sun, 16 Jun 2002 16:57:47 -0300 (BRT), Sebastiao Rocha wrote: >>> >I'm in! Could you publish it on the Pear CVS tree? >>> >>> IIRC there has been the decision some time ago that complete PHP >>> frameworks don't fit in PEAR's structure. >> >> If they can be broken up in smaller components, they fit well in PEAR. > And that is just what we are proposing. Using Pear independent packages and > create some dependent ones. If people wants to use Pear packages alone, > fine. If not use the peaces to make a Framework or part of it. > I think that independet components should be our first design requirement. > What to you think Jens? Your work can be separated in small components? Right now my framework is made up of several pretty tightly coupled classes. The main Controller class contains a lot of has-A relations to other classes, like the DB handler, session and request objects, ACL class, Locale, DB_Log and so on. This of course makes it pretty difficult to distribute it in separate components. Some of these classes could be easily used standalone with only minor code changes, but the main MVC part is per definition a composition of several related base classes, namely a Model, a View and a Controller part. But the DB package handles the composition of several related classes pretty well, too ;-) > S. Rocha > P.S.: Do that means that we can have a Pear CVS account? ;) I think it's no use to ask for a CVS account when nobody has seen the code, yet. So I set up a public CVS readonly account on my machine: :pserver:cvsread@bards-tavern.darktech.org:/usr/local/cvs Password is cvsread Module name is htdocs Make sure to use "cvs checkout -P htdocs", since I made lots of directory structure "refactoring", leaving many empty dirs in the repository. Additionally you'll retreive some base PEAR classes as well when checking out the module, since the hoster where I plan to use my framework has only a pretty old, not up-to-date installation of PEAR and there's no chance to circumvent this (other than moving to another hoster, of course...) The coding style isn't totally following the PEAR style, but I bet you'll still find your way through the code. I encourage everyone to check out my classes and give feedback. I just hope my DSL connection can handle the load ;-) -- MfG, Jens