Okay i'm trying to learn how to make an MVC. I quickly found out reading up on the concept and trying to put it in your code are two very different things. So far i have this idea:When the user goes to a page (website.com/index), the controller is activated and checks the url for a query string. depending on the query string (foo.com/view/action/param/param...) it grabs the view (contents of the page) from the view class and spits it out.When the user wants to log in or something, they would click a link that would go to website.com/view/login and i guess the view would pass parameters to the controller and the controllers sends that to the model, the model validates everything and sends back either an error message or logs the user in, the controller gets that response and sends it back to the view. Is this how it's supposed to work? And if so, how could you impliment this in code? I would really like to see an example if possible

Jeff_Mott
—
2013-04-23T00:53:43Z —
#2

First, an obligatory explanation:

[INDENT]The original definition of MVC was written with desktop applications in mind, and it doesn't translate perfectly to stateless, server-side web applications. For example, MVC controllers are supposed to handle user input -- such as mouse clicks, key presses, touches, gestures, device orientation, etc -- and translate that input into commands for the view and the model. But in server-side web applications, there's only one input: the HTTP request. Also, MVC views are supposed to be able to react to user input as well as to changes in the model, but in server-side web applications, there won't be any new user input for the view to react to, nor will there be any changes in the model that would require the view to update itself.

Because of these differences, MVC has typically been implemented differently for the web. Views became templates, and the templates don't access the model directly. Instead they are fed data by the controller, which acts as a mediator between the model and the view. It turns out there's another design pattern that more accurately reflects the way server-side web applications typically work, called Presentation–abstraction–control.[/INDENT]

With that explanation out of the way, I think we need to know which "kind" of MVC you're trying to implement before we can help. If you'd like to implement MVC in its original, purest sense, then @TomB ; can help you with that. Or if you'd like to implement the kind of MVC that today's popular frameworks are built on, then I and some others here can help you with that too.

Gotcha. In that case, I recommend the article From Flat PHP to Symfony2. This article starts with a traditional, flat PHP script, and it takes you step-by-step to reorganize it into MVC (or at least what frameworks such as Zend and Symfony consider to be MVC, which we now call MVP/PAC).

calebbee
—
2013-04-23T02:52:00Z —
#5

Thank you! I will take a look at this article.

calebbee
—
2013-04-25T01:49:32Z —
#6

I have looked at the article and started to try my hand at implementing a version of MVC. I want to ask a few questions though..First, i have a class that will try to get the ball rolling, but the autoloader won't work. Here is the code:

All of the classes i want to load are kept in the same folder..Also, a question about the way information is handled. I see others making a controller and a view for each page, but wouldn't it be better if there was one controller for each action that was going to happen? And having a template for each page and just including with a render method from the view with the page name passed as a variable?

Hall_of_Famer
—
2013-04-25T06:47:06Z —
#7

You will have to register your autoload method using spl_autoload_register to get it to work.

calebbee
—
2013-04-25T19:42:20Z —
#8

Ah thank you. I got the autoloader to work.Could i get some advice on the functionality?

Hall_of_Famer
—
2013-04-26T21:11:09Z —
#9

The functionality for what? The bootstrap class? Id say it looks good so far, although once your routes become more complicated than the simple pattern controller/action/params you may need a router class to handle url requests and a dispatcher to convert them into the appropriate form for your controller class to use.