Menu
Community /Pin to ProfileBookmark
@NogDogDec 09.2010 — #I would say your overall grasp is correct. In practice, many (most?) MVC frameworks use one index.php file as the point of entry. Based on the URL it determines which controller object to launch and which method to use as the entry point.
In practice, it seems a lot of people tend to put a lot of the business logic into the controllers, even though in theory it would belong in the models. To me that's generally academic, and I put it wherever it seems most expeditious to do so. ?
If you want to pursue a MVC implementation, I'd suggest using one of those frameworks unless you really want the "fun" of doing it yourself. But if you use one, then you have the advantage of not having to worry about that underlying substrate, testing it, optimizing it, and so forth: just go build the actual stuff you need for your site. I personally am a CodeIgniter fan, if for no other reason it was the first one I tried that "clicked" for me, perhaps in part because its documentation was very good. Zend has a big following, and is perhaps at a slightly lower level: giving you more power at the price of a bit more complexity.
[url=http://codeigniter.com/tutorials/]CodeIgniter video tutorials[/url]
Help trying to understand MVC logic
Ok guys,
I’m about to begin working on a sister site to my current site, however I want to start getting into the habit of moving away from procedural programming. Eventually, I’ll have to redo a lot of my code on my other site to make things cleaner.
Anyway, one problem I’m having is fully grasping the concept of MVC. From what I understand thus far:
Model = Data (or business logic)
View = Representation of Data (how the data will be formated and how the user will see it)
Controller = The connection point of what data to use and how it should be viewed.
From what I understand, all these are in the file structure as folders. I assume afterwards that if you wanted to create the index.php file, that you’d create a new file outside the MVC folders called index, and call the MVC class files respectively creating class objects where needed.
I assume also that the same concept would apply for say a newsupdates.php page where the database request would reside in the model, the html output and representation would reside in the view, and the controller would say get that data and use that view. If I’m also correct, you could essentially make another page called newsarchive.php and reference the same model used in newsupdate.php with the news archive view right?
Sign in
to post a comment2 Comments(s) ↴
0
@NogDogDec 09.2010 — #I would say your overall grasp is correct. In practice, many (most?) MVC frameworks use one index.php file as the point of entry. Based on the URL it determines which controller object to launch and which method to use as the entry point.In practice, it seems a lot of people tend to put a lot of the business logic into the controllers, even though in theory it would belong in the models. To me that's generally academic, and I put it wherever it seems most expeditious to do so. ?
If you want to pursue a MVC implementation, I'd suggest using one of those frameworks unless you really want the "fun" of doing it yourself. But if you use one, then you have the advantage of not having to worry about that underlying substrate, testing it, optimizing it, and so forth: just go build the actual stuff you need for your site. I personally am a CodeIgniter fan, if for no other reason it was the first one I tried that "clicked" for me, perhaps in part because its documentation was very good. Zend has a big following, and is perhaps at a slightly lower level: giving you more power at the price of a bit more complexity.