Of course the logging can be integrated in different manners. You can write a FilesystemLogger, or a DatabaseLogger, or, with less hassle and work, a PearLogAdapterLogger. But I don't see why a FilesystemLogger should also work standalone. That's not the point of a framework. If you want modularity, write your own, universal logging system, and then create an interface class so Agavi can use it. The way the implementation interfaces with Agavi should remain the same, no matter what the implementation looks like.
- David > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of zimba-tm > Sent: Monday, June 20, 2005 8:31 PM > To: Agavi Development > Subject: Re: [agavi-dev] Splitting up the framwork > > IMO, the difficult part about designing a framework is that you have > different people involved, with each party havind slightly different > goals. > > My point of view is that Agavi is there to build applications. Unlike > Drupal, Mambo and other big CMS, what I enjoy in Agavi, it's that I > can make most of choices myself. I have the advantages of having ready > to use tools, and at the same time I'm not stuck with unapproriate > technology choices. > > The interest of having different packages, is to make the framework > more decoupled. For example, the logging part could be integrated in > different manners. Then the choices made for the implementation would > matter less. If you want, you can name it a tool box, but unlike pear > we have the package that rules them all :-p > > I know it's not very concrete, so I'm actually trying something that > I'm going to show in 2-3 days. > > On 6/20/05, David Zülke <[EMAIL PROTECTED]> wrote: > > What are the exact reasons for splitting up the framework into > independent > > parts? I've seen some lines here and there about it on the forums and in > the > > wiki, too. I don't really get the point of it - if we have independent > > thingies, it's not a framework anymore but rather a plain, stupid > toolbox of > > utilities. > > > > - David > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On > > > Behalf Of zimba-tm > > > Sent: Monday, June 20, 2005 3:26 PM > > > To: [email protected] > > > Subject: [agavi-dev] Splitting up the framwork > > > > > > Would you mind if we split the framework into different parts ? > > > The main goal is to avoid too much coupling between the different > > > parts. So that different tries can be tested. > > > > > > To start with, I was thinking about : > > > - Logging > > > - ErrorHandler > > > - ClassLoader > > > - MVC > > > - Configuration > > > and the Skeleton application > > > > > > I was also thinking to use the Pear packages > > > > > > more to come... > > > > > > If you have any sugestions about how to manage dependencies and > > > version numbers, I'd be happy :) > > > > > > -- > > > Cheers, > > > zimba > > > > > > http://zimba.oree.ch > > > _______________________________________________ > > > agavi-dev mailing list > > > [email protected] > > > http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev > > > > > > > > _______________________________________________ > > agavi-dev mailing list > > [email protected] > > http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev > > > > > -- > Cheers, > zimba > > http://zimba.oree.ch > _______________________________________________ > agavi-dev mailing list > [email protected] > http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev _______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
