Oh, i can see something happening here ;o) http://github.com/fabpot/symfony/commit/22e310e24014f7873721359f7f3c7eca17b9b933
Michael On 22 Feb., 14:04, Fabien Potencier <fabien.potenc...@symfony- project.com> wrote: > On 2/20/10 11:03 AM, [email protected] wrote: > > hehe, good catch ;) > > To avoid downloading all the debug toolbar information in the same > request (as this can be quite huge), the debug data for a request will > be stored on the server and accessed on demand. > > Fabien > > > > > > > Michael > > > On 19 Feb., 20:36, Fabien Potencier<fabien.potenc...@symfony- > > project.com> wrote: > >> Of course we will have a default directory structure, and sensible > >> defaults for configuration. Actually, this is already the case if you > >> have a look at the sandbox. > > >> Flexibility does not mean that you have to use it. For most people, the > >> default will just work for them. But it's great to know that if you need > >> to customize something, that's just possible. > > >> Fabien > > >> -- > >> Fabien Potencier > >> Sensio CEO - symfony lead developer > >> sensiolabs.com | symfony-project.org | fabien.potencier.org > >> Tél: +33 1 40 99 80 80 > > >> On 2/19/10 3:42 PM, [email protected] wrote: > > >>> Very very very impressive Symfony 2 ... ! > > >>> I watched parts of the conference (thanks to Ben Haines), i read the > >>> blogs, i watched the slides, i tried the sandbox ... really, very > >>> impressive. > > >>> I also watched the presentation from Fabien himself (http:// > >>>www.slideshare.net/fabpot/symfony-20-revealed) and read features like > >>> "Extremely Configurable", "Name your configuration files the way you > >>> want", "Store them where you want", "Inherit them as much as you want" > >>> or "Mix and match configuration files written in any format" etc. > > >>> This sounds really nice. But even though it's possible, IMO Symfony > >>> should force us to use, or at least recommend us (the developers) some > >>> sort of structure for our projects. What i really like about symfony > >>> 1.x is it's common project structure. I mean, you always know where to > >>> setup the database, where the models are, wehre to edit the actions > >>> etc. Even if you have to start working on an already existing project, > >>> you know where you are. And i think this is a very important Symfony > >>> feature for bigger (enterprise) projects. > > >>> So the new possibilities are for sure great and endless, but i hope > >>> Symfony 2 will have it's own standard "project development pattern", > >>> like symfony 1.x ... > > >>> Can't await end of 2010 ;o) > > >>> Michael -- 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.
