On 10/27/10 8:14 AM, Lukas Kahwe Smith wrote:
On 27.10.2010, at 08:08, Fabien Potencier wrote:
With that code in the core, we can also probably provide some
generic View class implementations in the core (like the JSON
one).
That's a possibility... and something I wanted to talk about and
play with for quite some time now... but I just hadn't the time to
do so...
So, your question is good way to get the discussion started on that
topic :) Comments welcomed...
But this means the controller needs to be modified to make use of
this. But I do not want to change the business logic, all I want is
to change the view. IMHO therefore I should be able to take the
controller 1:1 and just mess with the view layer. Otherwise I will
run into the same issues over and over again with 3rd party
Bundle's.
Yes and no. There are two use cases. The first one is when you create a
controller/view/template for your application (no need for reuse here).
The second one is for bundles your want to share. In that case, there
are many possibilities. But not everything can be generic. This is just
not possible, nor desirable. We need to stop somewhere.
Fabien
Then again I assume we could take your approach further via the DIC
to make it possible to replace the default view layer without having
to touch the controller.
regards, Lukas Kahwe Smith [email protected]
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
