On Sep 24, 3:05 pm, Eno <[email protected]> wrote:
> On Wed, 23 Sep 2009, bghost wrote:
> > No offense Fabien, this is a well-meaning criticism. I know that you
> > invested so much effort into Symfony. However, you are a little
> > exaggerated forcing object model and object-oriented programming
> > where it is necessary - and where it is not (as is the case with WEB
> > Forms)
>
> I actually *like* the new forms framework. It is a better abstraction than
> cobbling together helpers in templates, coding the action and having
> validation in YAML files (plus another file if you had to write your own
> valiator). Having a form as an object and being able to do things like
> $form->isNew() or $form->isValid() is easier to me.
Some people like the new forms framework, but I think it will remain a
point of controversy. Let's remember that the core Symfony team
exploded into pieces because of acrimony over the new forms framework.
I appreciate the abstraction the form classes offer, but at a
theoretical level I haven't yet gotten my mind around it. What design
pattern is this? I jokingly said that Symfony now has a MVCF
architecture, but, more seriously, I'd be curious what other
frameworks implement something like this, and why?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony users" 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-users?hl=en
-~----------~----~----~----~------~----~------~--~---
