sfForm is the way to go, doing form the old fashion way (coding form
in template) is terrible.

It is not harder, it's just different from old ways of doing things.
It only seems hard because you're used to doing form the old ways.

If you have strong OOP background and design patterns, you'd love sfForm.

About documentation, I agree it needs improving but currently it is
still pretty good. Having said that, I could always find answers from
Googling.

If you gave up from just learning Jobeet, then that's a shame. It's
like trying to learn J2EE and gave up after half way reading a book
called "Learn J2EE in 30 days".

On Sat, Sep 19, 2009 at 7:27 AM, 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.
>>
>> --
> >
>



-- 
Blue Horn Ltd - System Development
http://bluehorn.co.nz

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to