Hi,
I do not se apparent MVC violation. I also do not get the point of that
"crazy guy". Is he talking about some theoretical MVC reference
implementation?
MVC means in general that you should think of separating data, actions and
presentation. That what symfony does. If you move controller code f
>
> Is he talking about some theoretical MVC reference implementation?
Yeah, I think he is. I think that his problem here is that it's *possible *to
build applications that go against the theory of MVC. I don't see this as a
problem, but I guess it's not an entirely idiot-proof solution - I agree
Hi Fabian,
Thanks for your response.
At 16:41 04/03/2008, you wrote:
>Without knowing more where you are aiming at, I cant help you further. If
>you could outline your scenario more we can tell you how you can do it with
>symfony.
I was thinking a bit too abstract to be practical. In the sense
Hi all,
to Peter's thought of automating the output-type decision of an
action
based on what type of request is coming in (unless I also missed
it ;) , I think that is actually a valid point that Mike "let's not
perpetuate the crazy-guy name" is bringing up. In his Agavi framework,
they treat req
-Original Message-
From: Peter Bowyer
Sent: Mittwoch, 5. März 2008 09:37
To: symfony-users@googlegroups.com
Subject: [symfony-users] Re: MVC separation in Symfony
Hi Fabian,
Thanks for your response.
At 16:41 04/03/2008, you wrote:
>Without knowing more where you are aiming at, I cant hel
Original Message-
From: symfony-users@googlegroups.com [mailto:[EMAIL PROTECTED]
On Behalf Of Fabian Lange
Sent: 06 March 2008 15:08
To: symfony-users@googlegroups.com
Subject: [symfony-users] Re: MVC separation in Symfony
Hi Peter,
- please turn your buzzword-detector off -
thats indeed a
