Options generally, by their very nature, are optional. Many of the default values are sensible and well chosen. Complications when starting to use framework aren't generally due to sf but usually due to how much experience people have with developing against MVC frameworks generally.
I guess that some people find the tutorials too complex - because it tends to explain the reasoning behind each stage. When following Jobeet - it's best to run through it quickly without trying to understand the "behind the scenes" explanation once, and then to repeat it once again to get a better understanding of the who, what, when and why. On Fri, 18 Sep 2009 17:04:08 +0200, bghost <bggho...@gmail.com> 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 <sid.bacht...@gmail.com> 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 <bggho...@gmail.com> 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 > > -- 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 symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
