Preface – This post is part of the Visualforce series.
Understanding the Model-View-Controller (MVC) pattern is essential to learning Visualforce.
HA! YEAH RIGHT!! There are only two reasons you need to know this mumbo jumbo:
#2 happens to be important, so I’m going to teach you everything about MVC.
That’s really all there is to it! I still think they should’ve just called it the DUI pattern just to keep things simple. That’s database, UI, interface. Fancy conversation.
Why do we use the MVC pattern? By separating our page into three different components, we get a more modular codebase that’s ultimately easier to maintain and more scalable.
This kind of reasoning should sound familiar to you by now. It’s the same reason why we use objects in Salesforce. It’s also the same reason why we use classes in Apex. It’s also why your tires aren’t permanently attached to your car. See? Everything in this world revolves around objects!
Next post: Where to write Visualforce code!
Haha, the MVC questions keep popping up on my 401 flashcards, I even sketched out the diagram from Wikipedia. Mumbo jumbo! By the way just checked out those Google jobs, looks sweeeet. Better put a few more java books under my pillow. Have a great weekend David!
Good luck Kevin in Oakland =)
Thanks David! This is great!
Glad to see new post David!
Please don’t forget to include the philosophy behind the each concepts going forward.
Many Thanks
Ravi