NikkiLoveGod Posted November 13, 2008 Share Posted November 13, 2008 Hi all! More stupid questions about MVC, that I haven't had a clear answer and just have to make my self clear. Right now, I am in a mindset, that the controller asks model for some information, puts it into a variable, and sends it to a views variable. This seems fine to me, but now i am having second thoughts. Should it be more, like that I STORE the data at the model as well? Like if I get the site navigation from the DB, and define what page I am currently on, should I store that information in the MODEL and have a method to call it from there, even from the view, or should I store the the info in controller's variable, and just send it to the view? Thanks alot in advance! -NikkiLoveGod Quote Link to comment https://forums.phpfreaks.com/topic/132502-clearing-up-mvc-each-parts-correlation/ Share on other sites More sharing options...
Mastodont Posted November 13, 2008 Share Posted November 13, 2008 controller asks model for some information, puts it into a variable, and sends it to a views variable Controller chooses view and view interacts with model. But controller has responsibility for updating model (adding data from form etc.) Here is nice summary: http://www.phpwact.org/pattern/model_view_controller Quote Link to comment https://forums.phpfreaks.com/topic/132502-clearing-up-mvc-each-parts-correlation/#findComment-689438 Share on other sites More sharing options...
NikkiLoveGod Posted November 13, 2008 Author Share Posted November 13, 2008 Thanks a lot Mastodont! You have been most helpfull! Those helped me alot! Now, on to my next problem, and next post! -Nikki Quote Link to comment https://forums.phpfreaks.com/topic/132502-clearing-up-mvc-each-parts-correlation/#findComment-689511 Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.