Marc Christopher Hall wrote:
The following comment is not intended to be helpful....

*smacks head on desk repeatedly...*

This comment is..

I would hazard to say that if you are unwilling or unable to grasp OOP, MVCs
and any decent framework that is necessary then maybe stepping back and
tackling only things you can grasp.

To be honest - one of the problems is that documentation that tries to explain these concepts is often severely lacking, using extremely poor analogies, and only make sense to people who already have an understanding of the concept.

For example -

A car is a good real-world example of MVC. With a car you have two views: the interior and the exterior. Both take input from the controller: the driver. The brakes, steering wheel and other controls represent the model: they take input from the controller (driver) and hand them off to the views (interior/exterior) for presentation.

That's from a web page that is suppose to explain MVC.

I bet if you took 50 people who didn't have a clue as to what MVC is - maybe 1 or 2 of them would after reading that.

Documentation and howto's, just like code, really need to go through real world testing to see if they make sense to people not already familiar with the topic.

Unfortunately that rarely happens.

PHP General Mailing List (
To unsubscribe, visit:

Reply via email to