Hey we're all learning... I've been using MVC for all of 4 hours ... which is how long it took me to install CodeIgnighter, watch 4 videos on the basics of CI... and then take my current development site and re-build it suing the CI MVC framework... So far I've only gotten the VC part of it going... tonight I plan to start getting some of the models set up.

Although, I do admit, I hit a snag where my AJAX no longer works on the site... but I saw a video tutorial for using AJAX, so I may watch that tonight and see if I can get that part working... then deal with the model bits... just depends on which I feel like tackling first.


One of the fallacies I keep seeing when it comes to MVC tutorials (and even the CI one does this) is they tend to tread the view as the whole page... rather than what it is: a view of a particular piece of data... very few of us build websites (or applications in general) that consist of a single entity... there's usually several view components on the page. Like my page: Header View, QuickLinks View, SideBar View, Footer View and the ever changing Content view... I even have a couple cases where the content view actually has two views... the primary content for that view as well as including the featured view...

It's all neat stuff... once I got my head around the concepts, and playing with the code, I could see the potential... and I get why it's so popular... and the fact that it's so freakishly easy to set up (as long as you have a base framework to start with.... I shudder to think what it would have taken had I tried to build something like CI myself... I'm good... jsut not THAT good.)

-tg