Re: [symfony-users] MVC vs module in Symfony

On Mon, 17 May 2010, Dennis wrote: > So anyone seen a definitive pictogram that shows all the elements of > Symfony in relation to an MVC implementation? Something like a Venn > diagram showing which element of symfony belongs in which part of pure > MVC? > > I'm kind of wondering most of all: >

Re: [symfony-users] MVC vs module in Symfony

Modules are a grouping mechanism for actions (controller) and their associated templates (views). Actions can access the model classes (model) to get the data needed by the templates (view), which is why the action is the controller; it controls recieving an incoming request (link clicked, form

Re: [symfony-users] MVC vs module in Symfony

Hi, >From what I understand : Model: Doctrine/Propel View: Partials, templates (sfPHPView engine) Controler: Action, Component Modules are containers for actions, to group them somehow. Cheers, Before Printing, Think about Your Environmental Responsibility! Avant d'Imprimer, Pensez à Votre Re

Re: [symfony-users] MVC vs module in Symfony

Hi, Sorry I've never seen such a diagram. There is an UML picture of symfony imternals. A module covers view and controller tiers in mvc, and yes you can define filters and forms on each module, or overload the generated ones, just pût them in module/lib folders. To disable filters in an a

[symfony-users] MVC vs module in Symfony

So anyone seen a definitive pictogram that shows all the elements of Symfony in relation to an MVC implementation? Something like a Venn diagram showing which element of symfony belongs in which part of pure MVC? I'm kind of wondering most of all: What role in MVC does a module perform?