@Luke, put your github account on social links too :)

Nice,

the URL tips on commets is very helpful, great post!

@ Volomike:
Reading this blog entry and especially your comments, I am now converting to MVC religion also.

Just an announcement. I’ve seen the light. I’m MVC all the way now. I mean, I was doing this sort of stuff, anyway, just not realizing it. The other day I started doing some control routing from incoming URLs, and then I said, “See? That’s the front controller you’re building.” I then started building a template class instead of using Smarty, and again I said, “See? That’s the view class.” So then I started learning about the difference between a front controller and page controllers, the purpose of models vs. controllers, and I then started evaluating frameworks. From there, I realized that the only way I would be satisifed was to make my own MVC framework, so I did it.

So, another angel gets his wings in heaven.

The missing url for routing is http://www.allseeing-i.com/Bare-bones-Rails-style-MVC-Request-Router-f or-PHP

From my personal use any CRUD functionality is in a parent model class that all models inherit from.

As for handling clean (sexy) URLs, having some kind of routing schema helps. Horde has such functionality – http://dev.horde.org/routes/manual/index.html, and there is another here, which can be integrated in setups like this.

sounds good, PM it over :-)

I initially wrote a long winded counter argument but after re-considering I really don’t think it’s appropriate to hijack this guys blog.

If you wish to continue disscussion start a topic in T & D at DN and I’ll likely speak my two cents. :P

Cheers,
Alex

Also saying using a base controller causes less flexible code doesn’t make sense, your controllers need convenience methods like accessors to request objects, factory methods for generating views. Using a base controller in my experience has helped me not repeat myself, not produce less flexible code. Majority of the PHP MVC frameworks have you subclass a controller_action class or something of the sorts.

Of course a controller action ( action level ) doesn’t require 100% of the time a dependancy to a model and a view, I’m saying in the MVC pattern the view fires events, the controller catches events. You are uncoupling the view from the model, by coupling the model to the controller. You can’t get rid of coupling you can only move it around to more desirable places. My argument wasn’t about how to write a CRUD controller but basically its called a state object, instead of subclassing an abstract class you have the object’s behavior change based on some internal flag, subclassing the object only for special case applications, since your controllers have an inheritance hierarchy you’re writing code only once. Less code? yeah, less controllers? depends on your coding style.