I sort of disagree here, though I see what you're getting at. Stripped down to it's extremely bare essentials, MVC is not that complex. You can distill it down to a one-page example (no front controller or other bits and pieces).josh wrote:As far as implementing your own MVC its definitely doable, but itd be like trying to learn about polymorphism by writing an object compiler. Definitely doable but IMO not the way to learn.
We can work through the raw basics of it (and I mean really basic) here. Let's take a simple example. Forgetting the rest of the application, and imagining that this is just one page...
You're a fruit retailer. You've got a database of sales that shows the numbers of each type of fruit in each transaction, along with the sale amounts. Now let's say the task here to is create a simple page that gives a table, showing the combined sale amounts for each type of fruit in any given month. The user should be able to change the month and the year in order to see the sales for that period.
I think this makes for a very simple model, an incredibly simple controller, and a very basic view. Should we do it?
I can see how people will get carried away applying other patterns here... keep it to the basics. We can work with superglobals directly etc for now.