|Some thoughts about sf 2.0 [message #97624]
||Mon, 19 April 2010 16:10
Registered: July 2006
I'm a faithful user of sf since 2006 and I'm waiting the 2.0 release impatiently.
Here are some thoughts I had during the reading of the 4 tutorials.
I will start by the things I like :
* integrating zend where it makes sense
* routing is great
* templates are more powerful than in 1.0 (I hope that twig, PHamlP and forms will be easily integrated later)
* doctrine and swift are also good
* the debug bar
* the documentation written so far is pleasant to read
* the config checking
* the error messages
* the format param to choose xml/json/html/...
Now, for the things I dislike.
The first thing I thought was the unnatural way to separate directories for the bundle and the config.
I think that bundles are more or less like the modules in sf 1.0 and so controllers, templates, connfig should be together.
I know this is surely possible thx to the config system, but why is this not the default (or why the doc dos not show it) ?
The tutorial shows how to install the sandbox inside the document root of the web server : this is really really really bad !
The next and final dislike is that I cant use sf 2.0 yet
Now for the things I am waiting :
Let's say that I have a CmsBundle and a ForumBundle, the two have a file called main.css in the css directory : they will override each other if I place them in the web directory...
In the same aspect (client side artefacts), I'd like an automatic js / css "combinator and minifier". That is, I place the css and js in the web_resources package of my bundle. Then when I call "js.php/mybundle/a_directory" I get all the js files combined and minified (of course, this combined and minified resource will be cached in prod environment and readable in dev environment)
Another thing is that the DI container and the event dispatcher named in http://symfony-reloaded.org/architecture are not in tutorial part 5. I know that the tutorial is for not so advanced use of sf, but the 2 pages are named "architecture"
Other things I hope for :
* integration of twig
* integration of PHamlP (i.e php port of Sass and Haml
* a tutorial showing a real webapp (i.e with db / ajax / DI / events / lots of css and js ...)
Now for the thing I'd like to know how it work :
* I saw that I can have params to an action (like indexAction($name)) :
* how is the mapping done from the request to the parameter of the function ?
* If this is done thx to reflection, how do you do with a a php compiler like apc ?
* Is there magical params like $request or $culture or i18n or mailer or ... ?