Depending on our needs we can write custom functions in our Models and than assign a template depending on parameters returned by a function.
just before the addCss section
I am not sure how MVC is implemented here, my understanding is the the Model layer is mainly for Databse interaction which then hands info to the controller, also looking at the files the files under the Model folders do a lot of work.
what is the criteria for adding stuff to a model instad of a controller for magento?
this may be the wrong section of the forum, but i thought i would add it here as i am talking about how the model is related to the view based on the above wiki link.
Thank you for reading carefully the post. It should have been read as “blocks” not “models”.
The charts explaining the architecture of Magento will be posted as soon as we’ll get to it, but meanwhile here’s short overview:
- Model
To allow greater flexibility with backend implementations, we have splited these to Object Models and Resource Models. Object Models are responsible for abstract logic of the models and Resource Models are for engine specific logic.
- View
Here we have Layouts, Blocks and Templates. Layouts are XML files defining Blocks tree structure and specifying Templates for them to use.
- Controller
these are the Zend_Controller_Action compatible classes.
Thank you, will wait for charts & architecture, for a better understanding, just want to know if this is a standard pattern that you guys decided to follow, or if its a new concept you have come up with ie is it a standard documentent pattern that i can read up on a litlte more at wikipedia or somewhere?
