If you weren’t convinced by the first 5 reasons why Symfony rocks, you will certainly be today.
Symfony’s closest competitors are probably RoR or rolling your own framework. Using a pre-made framework instead of rolling your own has several advantages:
- Easy collaboration between coders, because of standardized approach
- A framework developed by many will include nice features which you wouldn’t bother to implement on your own
- You can outsource part of your development easily, or if you serve customers they receive a product their own developers can easily work on.
- Working in a framework not developed by you teaches you the practices of other developers (some of which might be good)
Lets see the final 5 reasons why Symfony rocks. My chosen 10 are just a small subset of the powerful capabilities of Symfony and I will link to all good blog posts covering this topic. (Current Symfony version as of writing is 1.0.7)
1 – Internationalization and Localization (i18n & L10n)
Symfony offers a really fantastic suite of internationalization tools. I suppose the fact that the creators are in France has something to do with it. The simple comment example of the last post actually gives us a nice start to show the possibilities. We will support these nice languages: (English, Dutch, Italian and Romanian – the last two thanks to my girlfriend).
As mentioned Symfony provides a full solution. For the basic translation needs Symfony uses a helper function with two underscores, as such: __(‘text which will be translated’). The text which needs to be translated can be exported to an XLIFF format using a plugin (Will be part of Symfony in 1.1.0) . For those wondering the XLIFF format looks like this:
A simple config setting deals with the usage of utf-8; Formatting for numbers and dates are available and use the culture automatically. format_date() and format_number() automatically adjust their output depending on the culture.
Best of all the data model supports the concept of I18n tables. This allows you to have translations of items in your database (for instance products) and leave all the logic of dealing with this to Symfony. More advanced translation needs such as sentences, which depending on the database results need to be pluralized are also supported.
Lets look at the possibilities using the simple comment example. Implementing these languages is achieved in a few simple steps:
Firstly Symfony needs to be configured to support translations. This feature is turned off by default for performance reasons. To do this simply uncomment the commented lines in frontend/config/i18n.yml and set the following settings in frontend/config/settings.yml:
Secondly we need to tell Symfony how to change the URLs, which we do in routing.yml. We will use URLs like this symfony-examples/nl/comment. Thirdly we need to actually use the interface translation helper __ on all our text, as such:
I happened to forget the submit button the first time around. This is a rather tedious process and you would usually do this while you create the template and not afterwards.
So now the fun of actually translating. First we create the messages.ro.xml and run the command: symfony i18n extract frontend ro. This command uses the plugin to extract the text, which needs translating. After some translating we now have a nicely internationalized version of the comment example. Go see and click the flags!
Those cute flags were created by famfamfam
Read More: Internationalization in the Manual
2 – Caching
Caching is essential to the performance of any website. In many situations you can mess everything else up as long as your caching is good.
When reading about frameworks you will likely read that Symfony is somehow slow. Now off course you start to wonder whether this is true given that Yahoo uses it for its bookmark service. My impression is that these tests either use oversimplified ‘hello world’ examples or forget to query the database efficiently. A proper tests of speeds has to my knowledge not yet been conducted. Symfony is in fact lighting fast and offers a wide array of caching tools:
- Cache of an action (with or without the layout)
- Cache of a partial, a component, or a component slot
- Cache of a template fragment
- (plugin) sfArrayCachePlugin to cache an array
- (plugin) sfSuperCache Plugin to cache pages fully statically
- (snippet) Some work on a memcached plugin has already been done, which will be interesting for our developers fortunate enough to need it. (didn’t test this personally)
- Function result caching with sfFunctionCache
- sfProcessCache for memory caching with the help of PHP accelerators
In order to make the nice comment example nice and fast we will add some simple caching to it.
This enables the cache, however we do want to clear the cache when someone submits a new comment. This is easily achieved by adding the following to your update action:
$sf_root_cache_dir = sfConfig::get('sf_root_cache_dir');
$cache_dir = $sf_root_cache_dir.'/frontend/*/template/*/all';
This looks a bit complicated, but these four lines of code deal with deleting the cache for all languages.
Read more: Caching in Symfony
Read more: Memcached
3 – Development environments
Environments are a great way of running a few different set of configurations next to each other. This comes in extremely handy for development. By default Symfony has two environments: production and development. In the later all the caching is disabled, errors are displayed and the WebDebug toolbar is available.
When I wanted to setup caching these environments came in very handy. Somehow my comment form was not updating as it should. To diagnose the situation I added another environment called test (accessible by frontend_test.php), similar to dev, but with caching enabled. It quickly became clear that the problem originated from caching, client side to be specific.
For every larger application you will need to keep track of these different sets of configurations and Symfony enables this with great ease. To access the various environments simply browse to the corresponding front controller (index.php for production, frontend_dev.php for development, frontend_test.php for testing.)
To set the configuration settings, simply specify the config files as follows (example from standard frontend/config/settings.yml):
all: .settings: escaping_strategy: both escaping_method: ESC_ENTITIES standard_helpers: [i18n, Partial] charset: utf-8 i18n: on cache: on prod: .settings: no_script_name: on dev: .settings: # E_ALL | E_STRICT = 4095 error_reporting: 4095 web_debug: on cache: off no_script_name: off etag: off test: .settings: # E_ALL | E_STRICT & ~E_NOTICE = 2047 error_reporting: 4095 cache: on web_debug: on no_script_name: off etag: on
Read more about: Development Environments
4 – Do not repeat yourself!
All coders live by the rule of not repeating yourself. Symfony tries to make this as easy as possible for you. This is completely integrated into all aspects of Symfony. You can for instance write your own: Propel Behaviors, Filters, Validators and pretty any piece of normal code. This is one of the things which you will really like in Symfony. As a starter and to keep it short I’ll just cover the DRY tools in the view layer.
In Symfony there are four important methods to not repeat yourself in the view layer:
- Component Slots
A partial is a simple piece of repeated template code. Say that you want to have the ability to add comments on multiple parts of your website. Simply stash the template code for adding comments in a partial. Partials are stored in the template directory with a _ (single underscore) before the partial name. When you want to include them simply use:
<?php include_partial('module/partial',array('varinpartial' => $myvar)) ?>
When the code to repeat becomes more complex and also requires some logic we can separate the logic and template code by using a component. Suppose for instance that you created a blog using Symfony and want to display the latest blog posts. The logic part of querying the database goes in a components.class.php file and the template in a partial. This gives you a very convenient way to reuse code. Including goes as follows:
<?php include_component('blog', 'latestposts') ?>
Slots are placeholders. You can define its content anywhere in the view layer. This is great if you for instance want to have a default sidebar in your layout, with the ability to overwrite it in the template.
The really interesting one is the component slot. This combines the power of the configuration file with logic and view separation. It functions very similar to a component, except that logic part to execute is indicated by a config file. As follows:
sidebar: [bar, user]
sidebar: [bar, options]
This would make the component slot display a user related sidebar by default, but on the index page display no sidebar and on the page displaying the user data display a sidebar with options.
Read more: Symfony’s View Layer
5 – Bridges to other frameworks
A short, but important point. Both the Zend framework and EZ components offer quite some valuable tools. Symfony feautures bridges to both of these, giving you access to two large arrays of tools.
This allows for nice things, such as an instant search engine for your site, using Zend Search Lucene (released just days ago). There is always a lot of discussion regarding the so called best framework, but I believe that eZComponents and Zend are actually pretty complimentary to Symfony.
These 10 points showed some of the power of Symfony. Hope you enjoyed them and will run over straight to The Symfony Documentation. If you like Symfony then Digg this post up and spread the word!