We discussed a went thru the whole abstraction, mvc actual usage etc...
I need to read the Book by Jeff Peters Fusebox 4 & FLiP
You guys should have been here...
---------------Evening Class Notes ----------------------
Long argument about long vs tiny urls, I thinks i've hit a hot-button...
xfa = exit fuse actions, actions by which we exit
This brings up the question of what really makes a good framework?
1. Invisible and usability to the end user - They have no need to know what framework we use, except for what page they are at, and how to get to where they want to go.
2. Easy Setup & Install - Each time you create an application, if you have several hours just spent on setup, it makes no sense. What's better is a simpler or pre-packaged installer, so you can spend time planning & developing and not just more configuration.
3. Simplified workflow either working individually or on teams
Now abstraction has some interesting features, but if your not familiar with the framework and abstraction, it can be painful trying track down where variables and data are populated and created.