While for the trivial tasks it's overkill - generally you wouldn't use sf for trivial tasks. The current UI approach does encourage & promote reuse - which is often overlooked and a practice that's only slowly making it's way from the programming community to others (such as designers). The UI side of things in sf could do with some approaches to make it more friendly - to both designers and developers - but the issues are generic to most interpreted languages.
Symfony is a framework that provides a good clear API for software engineers who wish to design flexible scalable applications. It's not for HTML "programmers" or markup writers - mostly because those who design approach and tackle problems differently to those who engineer software. Now with sf you can knock up a prototype application very quickly - both with an interface for users and administrators - and without having to write very much code. It won't look pretty and it won't have much in the way of business logic - but that's why people who write software are paid :) Depending on your experience both of PHP and sf - you may not find the code very easy to read - but this is just a matter of experience of them both. Whatever your background in other languages - there's a learning curve to using and developing with something new. But don't throw the baby out with the bath-water - you started to use sf for a reason. Just take the time to work though the issues your facing, embrace the pain of the learning curve and I'm sure you'll find it worthwhile. Generally the documentation is very good esp compared to other PHP frameworks - but it lacks a lot if you compare it to that put out by MS & Co. This is something that should be addressed - and will be with time. Hopefully with sf 2.0 we can address and back-work some of the effort to 1.x. On Fri, 18 Sep 2009 21:27:16 +0200, bghost <[email protected]> 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. > > WBR, > Ghost3D > > On Sep 18, 7:26 pm, Eno <[email protected]> wrote: >> On Fri, 18 Sep 2009, bghost wrote: >> > - Symfony WEB forms are a bit too complicated and their relations >> > with the rest of a Symfony application is often unclear. >> >> This is a valid point: the definitive guide does not talk about the new >> forms framework very much. It also doesn't talk enough about the >> Doctrine >> ORM. If the separate docs could somehow be integrated into the defintive >> guide, it might help. >> >> I should also point out: symfony probably has the best documentation, >> forums, mailing lists and books that most other frameworks. >> >> -- > > -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
