On Tue, Mar 3, 2009 at 4:05 PM, Veikko Mäkinen <[email protected]> wrote: > Also, plan your module structure before creating the project. For a > simple web application it is common to have Public and Admin modules but > that gets too restrictive very quickly so instead, it is usually better > a module for every "section" in your application. Yes: even with my extended tutorial blog I have ended up with directories with quite a few files that makes just navigating between things a bit time consuming. I will be separating into modules.
> P.S. Remember to take advantage of module's base classes (action, view) > to keep common functionality in one place. Module's also have their own > autoload.xml Thanks! _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
