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
