Yeah, what a horrible idea to establish a framework that can standardize the code in multiple projects and code written by multiple people in the same project. It's better to start from scratch every time so that everyone's code works differently. Then when it comes time to maintain the code, you get to figure out the application's structure for each project and hopefully each person's code who worked on the project!
Quick note: WASP does use the MVC paradigm. Here's a link to the MVC portion of the sample application tutorial. http://wasp.sourceforge.net/content/?q=node/7#Mode l.2C_Views.2C_and_Controllers
Yeah, what a horrible idea to establish a framework that can standardize the code in multiple projects and code written by multiple people in the same project. It's better to start from scratch every time so that everyone's code works differently. Then when it comes time to maintain the code, you get to figure out the application's structure for each project and hopefully each person's code who worked on the project!