Most books I pick up on coding that discuss the MVC pattern in a way that suggests if you picked up the book, then you should already have an understanding of the pattern. Being very new to coding and OO principals in general, it's still unclear to me, so hopefully you help.
The model is where the code goes that represents the database, correct? I hear the term 'business logic' a lot, but that's very vague to me - what exactly is 'business logic?' what other code goes into the model other than database, if any? The view I think is pretty straight forward - it represents what the end user will see. The html templates sprinkled with just enough code to populate the content? The controller is the gateway into the application? It coordinates data from the model and view to mold together a 'finished product?' I'm still unclear as to what the controller is as well. If you can help better explain, that would be great - more layman terms while I become comfortable with OOP concepts. In fact, if you were explaining it to a non computer programmer or just-beginning computer programmer, how would you explain it? Thanks! Blue --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
