The most easy thing to understand is something that doesn't need
documentation and I believe that THIS is the point that BGhost is  talking
about."I don't want launch a rocket in 30 days, I want my gallery ready in
12 minutes..."

On Fri, Sep 18, 2009 at 12:26, Thomas Rabaix <[email protected]>wrote:

> Symfony has many components, each of them are :
>
>    - easy to understand
>    - easy to configure
>    - very well documented
>
> Now, the only thing complicated is to know how all these components play
> together. This is the tricky part, but symfony default configuration will be
> fine for many projects.
>
> You just need to go further ... if you have already create/try to implement
> a framework, you will see that symfony has all STABLE the pieces you need.
> Try to use an IDE : netbeans or eclipse, these two IDE are great to navigate
> across the code and understand it.
>
>
>
> On Fri, Sep 18, 2009 at 5:04 PM, bghost <[email protected]> wrote:
>
>>
>> Hi Fabien,
>>
>> - With the introduction of the Doctrine ORM, number of parameters
>>  and configuration options are increased manifold. Therefore, the
>> developer
>>  must first learn all about the Doctrine ORM. Is that good? Doctrine
>> ORM
>>  already providing a fairly good possibilities and options without
>> Symfony.
>>
>> - Symfony WEB forms are a bit too complicated and their relations
>>  with the rest of a Symfony application is often unclear.
>>
>> WBR,
>> Ghost3D
>>
>>
>>
>> On Sep 18, 4:43 pm, Fabien Potencier <fabien.potenc...@symfony-
>> project.com> wrote:
>> > You say that symfony became too complicated, which implies it was not
>> > before.
>> >
>> > Can you give us some examples of what became more complicated? That will
>> > help us improve the framework.
>> >
>> > For instance, we have less and less configuration files. Since 1.0, we
>> > removed a lot of them, and removed some parameters also.
>> >
>> > Thanks,
>> > Fabien
>> >
>> > --
>> > Fabien Potencier
>> > Sensio CEO - symfony lead developer
>> > sensiolabs.com | symfony-project.org | fabien.potencier.org
>> > Tél: +33 1 40 99 80 80
>> >
>> > bghost wrote:
>> >
>> > > First, I would like to say that Symfony framework is not too bad,
>> > > because I follow its development from the first version. But I think
>> > > it became too complicated because it is evident exaggeration
>> > > with the introduction of countless parameters and configuration
>> > > files in order to automate all possible tasks. This entails that the
>> > > programmer spends more time dealing with the Symfony framework
>> > > than with the real problem.
>> >
>> > > P.S. I did nothing special but just followed the Jobeet tutorial.
>> >
>> > > WBR,
>> > > Ghost3D
>> >
>> > > On Sep 18, 4:24 pm, Sid Bachtiar <[email protected]> wrote:
>> > >>> It is necessary to invest so much effort to do a relatively simple
>> > >>> application.
>> > >> If you're just learning Symfony, then yes of course you'll find it
>> too
>> > >> much effort. This is true with any other framework/technology.
>> >
>> > >> But for those of us who have invested our time in Symfony, we find
>> > >> great leverage in using Symfony.
>> >
>> > >> So what is the relatively simple application you're trying to build?
>> >
>> > >> On Sat, Sep 19, 2009 at 1:58 AM, bghost <[email protected]> wrote:
>> >
>> > >>> It is necessary to invest so much effort to do a relatively simple
>> > >>> application.
>> > >>> Productivity and profitability of such work is very questionable.
>> > >>> So, Symfony - Goodbye
>> > >> --
>> > >> Blue Horn Ltd - System Developmenthttp://bluehorn.co.nz
>>
>>
>
>
> --
> Thomas Rabaix
> http://rabaix.net
>
> >
>


-- 
Sidney G B Ferreira
Desenvolvedor Web

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