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

Reply via email to