Hi David,
I'm just starting a new project and I plan to use agavi. See my remark
below:
David Zülke wrote:
2) Give all classes an "Agavi" prefix to avoid name clashes. This will
include all classes that are shipped with the framework
Are these for internal classes, or classes that may be used by a project
using agavi, or both? If they are inteface classes, wouldn't it make
more sense to adopt a mojavi prefix for future compatibility? Or is
Mojavi 4 going to so different, that it wouldn't matter?
I'm just thinking in terms of where I'll be down the road if I use agavi
1.0 as my framework.
Thanks for your consideration.
Regards,
John Dell
_______________________________________________
agavi-dev mailing list
[email protected]
http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
