Hey guys, now that Agavi and Mojavi projects will be merging, the roadmap for Agavi certainly is changing a bit. I do tho think that we definitely have to ship a "final" or at least a new version of Agavi, even though it will not include all the features and changes that were originally planned, and that's basically what we agreed on in IRC as well. So I decided to just go ahead and propose a list of things that should make it into Agavi 1.0 (I think it should have this version number). The sooner this is released, the sooner we can fully concentrate on Mojavi 4, so I'm not adding any heavy things anymore.
1) Remove AgaviObject. It's not really necessary, the toString() method is never ever used anywhere. Just bloating things up 2) Give all classes an "Agavi" prefix to avoid name clashes. This will include all classes that are shipped with the framework 3) I'd like to merge in my View enhancements once I tested them. They're pretty minor, but they are crucial if we don't want the recent change that made execution filters pluggable to be totally pointless 4) I think the error_handler proposed by... was it Mike? sounds like a good idea That's it basically. Let me know what you guys think, and what else you find worth having in a 1.0 release. - David _______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
