symfony 1.3
Ideas for symfony 1.3. Keep in mind that we won’t add many new features in 1.3. We are mostly looking for things that can be enhanced and/or optimized.
-
focus on performances
even if there are a lot of ways to increase, we must admit that symfony is not the fastest framework by default, and we should therefore focus on making it faster
844 votes -
Improve sfGuard
I think sfGuard needs to be improved. Its pretty much the de facto standard user plugin for symfony and its not even finished.
I have had many problems with it and I feel it could be a bit more decoupled. I do not want to use a username and a password.. let me swap it out.
Hell.
At least finish the lost password feature.
610 votes -
I18n on url/routing (translate name)
en: /about
fr: /apropos
etc...on the same module/action
359 votes -
Make form framework simplier (shortcuts)
Something rails-like ..
$this->addInputWidget('id');
$this->addInputWidget('name');$this->addRequiredValidator('name');
284 votes -
280 votes
-
Add ability to use classes for helpers
Add ability to use classes for helpers instead of functions in global namespace.
223 votes -
Add support for jQuery and Dojo (and other JS libraries).
In the same way we support mutiple ORMs now, it would be great to support multiple JS frameworks and allow developers to choose what they want to use on a per app or per module basis.
221 votes -
210 votes
-
Complete the API documentation (like the Java one)
Complete the API documentation (like the Java one). All the parameters, examples, ...
170 votes -
use git instead of SVN
Please use git to track Symfony source code instead of SVN.
This would ease the collaborative development process.
139 votes -
108 votes
-
Add support for symfony test:(all|unit|functional) in plugin
It should be great to have the support of tests for plugins. For now, we can't run tests by plug-in
99 votes -
Extend the sfForm framework to create multipage wizzards.
Extend the sfForm framework to ease the process of creating multi page forms, with data access across each form part.
91 votes -
Add abitity to use custom myPHPView class
Add abitity to use custom myPHPView class (definied in factories.yml, for example), witch extends sfPHPView. Or at lest add ability to decorate not only templates, but partials too.
86 votes -
78 votes
-
a system vote and comments for plugins
a system vote and comments for plugins
69 votes -
Webservices integration
Webservices are the weakest point of current frameworks, because they do not have a full integration of webservices (MVC+ORM)
For example, now, ckWebService plugin exist, but ... many usefull features are not implemented or the plugin has some bugs, so i had to create what i needed from scratch...
I suggest, embed in symfony 1.3 something like CkWebService to deal with webservice.
Improve ckWebservice to restore the sfContext with the webservice front controller.
Find a better way to deal with soap headers.
Make usable the standard symfony permisssion management systeme in the webservices context.Find a way to translate propel… more
68 votes -
implement a (simple yet powerful) template engine
I guess we're a lot to be fed up with raw Criteria instanciations or algorhytmic code writeen right into templates : we should have a decent template engine, with template inheritance, as it already exist in other frameworks like django
66 votes -
postgis
make postgis and mapserver abble with the plugin system
60 votes -
57 votes
