Benjamin Börngen-Schmidt wrote: > Well, of course you need to know what you want to code. Set > Milestones, choose the basic tools you want to use (like propel, > mootools etc.), Copy ze Agavi Templates and edit them to your need, > before you even do agavi project-wizard. > Setup Agavi (DB, Logging, etc.) >
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. -veikko 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 -- Veikko Mäkinen [email protected] 044 5910 413 http://blog.veikko.fi _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
