On 19.09.2009, at 06:36, Jake Barnes <[email protected]> wrote:
> > > > On Sep 18, 3:36 pm, Lukas Kahwe Smith <[email protected]> wrote: >> On 18.09.2009, at 21:27, bghost wrote: >> >> >> >>> I think that the attempt of putting the entire WEB form within the >>> class >>> only unnecessarily complicate such a simple thing such is form >>> handling. >>> That's just forcing WEB developers to learn how to make simple >>> things >>> on the complicated way. >> >> i think this is a valid criticism. there is a clear shift away from >> having just some html/css/js guru do the templates back in symfony >> 1.0 >> towards requiring a symfony expert to also handle the templates, but >> that person lacks the html/css/js guru knowhow. the pay off is >> however >> that a symfony expert can now do a lot more if he just sits down with >> the html/css/js guru to create the required widgets in pair >> programming. the quality of the site should also increase since reuse >> is done more on the widget side of things but more importantly you >> start to bring everything data related together in the models, so you >> have a single definitive source. >> >> so what does it all mean? teach your symfony experts some more html/ >> css/js, teach your html/css/js guru some symfony .. or better yet .. >> facilitate paired programming .. and you should be off producing high >> quality more maintainable sites in less time .. but the old workflow >> of clear work separation isnt going to cut it anymore. then again, >> you >> can still keep the spirit of 1.0 in 1.2 i guess .. > > > You can still get the 1.0 spirit, though paired programming is not the > way to do it. And yes, for some projects, it is very important that > the designers have access to all of the HTML, including that in the > forms. Some design lead projects suffer badly from the default forms > setup in Symfony 1.2. err i was saying 1.2 projectscan benefit from paired programming while 1.0 projects allow for a clear separation. though that is not to say that paired programming even has its place there. > What's needed is a plugin that can auto-generate the CRUD forms in > nearly pure HTML, with PHP commands only handling the values that > appear in the inputs. That way, depending on the project, you could > either work with the default forms generated by Symfony, or switch > over to a system that is much more open for designers. > > If I get some time later this year, I hope to work on such a plugin. sure that could be a useful addition. maybe eith some magic comments there could even be the possibility to update or at least alert of inconsistencies. Regards, Lukas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
