php devs - mvc worth it or not?

There's a lot of talking around mvc at the moment in some php circles, worth dialing into it or is it simply another gimmic?

Mods - have dropped this in here as it's a general question not a php issue. :wave:

I've been dialed into it for a couple of years now... it has it's purpose... it's another tool... just like anything else... it's not a silver bullet or the end-all, be-all ... I've been using the CodeIgniter platform. I like it.

-tg

Well, I prefer mvc because it keeps things seperate and I am not that good at php.

NW - we pretty much keep things separate as a design method, easier to maintain that way.

At the moment not seeing mvc as in anyway speeding up our production, back to rewriting again after deciding we can't drop a product on people without it being OOP :( Gee third rewrite this year, will it ever hit the web?

You might find some info on google helps explain it. I found some links but accidently redirected the wrong tab I had open to a different page and lost all I had typed.

"At the moment not seeing mvc as in anyway speeding up our production" -- really? I'm finding the opposite true. At least when it comes to some web development. I think it took me longer to write an add-in module than it did to build the website. Granted it wasn't until I actually understood how MVC works, and but it to use in development that I actually grasped the whole concept and can now see how it benefits development. MVVM on the other hand, still escapes my understanding.

-tg

tg just making sure we are on the same page.

http://en.wikipedia.org/wiki/Model%E...0%93controller

I fail to see the difference between this approach and the current 3 tier approach we inheriated from the old vb5/6 days. Both allow for separate testing and development of components.

Currently we're looking into separating out the SQL statements into their own class(es).

Presentation

Logic and rules

Database/XML/ini