]]>
]]>
Ce type d’évolution est révélatrice de la direction que prennent les frameworks Java à l’heure actuelle. Ils cherchent à simplifier le travail des développeurs et essayent de combler le retard qu’ils ont à ce niveau par rapport à leurs équivalents d’autres langages (Symfony, Ruby on Rails,...). Il est assez amusant d’ailleurs de remarquer que pendant que les frameworks java se simplifient, leurs "concurrents" comme symfony deviennent plus complexes. Ces derniers reposent sur une utilisation de plus en plus poussée du modèle objet pour des fonctionnalités auparavant réalisées de manière procédurale (ex : sfForms). Si cela apporte des bénéfices en terme de robustesse et maintenabilité, la courbe d’apprentissage en prend un sérieux coup... Si ces mouvements continuent, il viendra peut-être un jour où les développeurs Java se moqueront de PHP pour sa complexité... Espérons que d’ici là, chacun arrivera à un juste milieu !
Today is the day a great portion of the community has been waiting for, even without knowing that it will be today. As our early Christmas present, we finalized the 1.2 release of symfony after some weeks of hard work. We will be revealing more presents soon, stay tuned :-)
Aims to catch and deal with most, if not all, errors within Symfony
]]>
After lunch, Dustin Whittle talked about the "Lessons learned at Yahoo" and Fabian Lange gave some tips on "symfony performance". That was enough for symfony. So, Jonathan Wage came on stage to talk about Doctrine.
The symfony web debug toolbar is one of the developer best friend. It is always conveniently accessible in the browser when using the development environment. It gives you everything you need to know about the current page and ease the debugging of your applications. Until now, all the information available in this toolbar were hardcoded. But as of symfony 1.2, the web debug toolbar is entirely configurable.
Un important travail réalisé pour la sortie de Symfony 1.1 a été le retrait du pattern singleton du framework. On peut maintenant instancier plusieurs objet sfContext par exemple. Cela permet notamment de faire des liens inter-application a peu près proprement. Voici l’avancée de mon travail sur la question :
As you may know, we have been working for a very long time on the next stable version of symfony. Now the day has come to celebrate the immediate availability of the long awaited 1.1 stable release of the symfony framework!
Before we release symfony 1.1 later this week, I want to give some information about the new symfony 1.1 architecture. Apart from the new exiting features we have in symfony 1.1, this version also represents a year of hard work to refactor the internals. Let's dig into symfony internals a bit!
The sfStatsPlugin provides an easy way to display charts based on data you already own. Whether you want to follow the global progress of your application usage, or to analyze precisely how many specific actions were done by users under particular conditions, this plugin is for you. Based on a simple YAML configuration file, the plugin will take advantage of the methods from your Propel Object Model to display a nice line chart from Google Chart API or a jQuery flot.
symfony 1.1 introduces native support for different formats and mime-types. This means that the same model and controller can have different templates based on the requested format. The default format is still HTML but symfony supports several other formats out of the box as defined in the factories.yml file
Starting with symfony 1.1, it is now possible to easily use Propel 1.3 in your project to take advantage of its speed improvements, nested set implementation, object instance pooling, among others. Most importantly, Propel 1.3 uses PDO instead of Creole as the DBAL, offering a significant performance boost. Un vrai argument en faveur de l'utilisation de Symfony 1.1
The sfAdvancedConstPlugin is a symfony plugin that provides app wide constants functionality. It automatically generates constant values based on sfRefTable values and make them accessible in every app module. It works the following way - go through the tables defined in sfRefTable and generate for each id / name pair from this table constants. This plugin is different from sfConst plugin which required to keep all the constants directly in sfConst table and did not require ref tables. Effectively, both plugins are usefull to be used. Installation
The sfSyncClusterPlugin introduces a symfony sync-cluster task. The symfony sync-cluster task is intended as a replacement for the symfony sync task. While the plugin is backwards-compatible with symfony sync (they even use the same configuration files) this plugin offers several advantages over a traditional symfony sync. The symfony sync-cluster task: * Synchronizes a Symfony application across an unlimited number of servers. Symfony's sync only works for a single server. * Clears the Symfony cache on each server with a symfony cc. Doing this with sync requires an additional command. * Allows you to use ssh public/private keyfile authentication so you won't be prompted for a password during long deployments. * Allows you to deploy your web assets to a CDN without having to copy your entire site. The sfSyncCluster currently supports standard rsync transfer and transfer to Amazon S3. * Allows you to specify groups of servers to sync. If you have many servers, you can place them into logical groups and move them around quickly.
Here's a helper that allow to generate cross apps urls in symfony 1.0
Login form in Symfony 1.1, with the new form system Symfony 1.1 comes with a complete new form system. It works completely according to the MVC draft: * Model: the validation * View: the form self through widgets * Controller: the form class that the model and view parts manages and uses Make sure you have a running Symfony 1.1 based project and application and modules. In this example I build the form inside the myModule module and myLogin action. My form makes use of i18n, which is in my case autoloaded in settings.yml. This tutorial uses Symfony 1.1 beta4 and RC1.
Among the remarks have about symfony 1.1, the most recurring one is the shift of philosophy between the 1.0 and 1.1 syntax. If symfony 1.0 syntax was made to write code fast, I believe it is not the case anymore with symfony 1.1, which is designed primarily for extensibility. The result is that a symfony 1.1 application looks a lot more like a Java program. I tend to agree that Object-Orientation is a good thing because it forces you to organize your code in a modular way. But when object-orientation makes you need to keep a symfony book aside at all times and multiply the number of LOC by two, I think it's a dead end.
Cela permet d’avoir un formulaire d’upload avec une checkbox pour la suppression du fichier. Si le fichier est nouveau un nom aléatoire lui sera attribué, sinon il remplacera l’ancienne version du fichier et ce sans écrire une ligne de code.
This tutorial shows how fast you can develop with symfony. It showcases symfony's admin generator capabilities, and makes great use of a couple of symfony plugins.
Sometimes, the price of a request when dealing with a symfony application can be overwhelming. But instead of getting back to spaghetti PHP, maybe you can get a handful of symfony features for a share of its initialization time.
To CASify a Symfonyapplication, first install phpCAS. Then, in your application's lib folder, create sfCASRequiredFilter.class.php with this:
Symfoclipse is a plugin for the Eclipse platform that ease the development process of web applications using the Symfony framework. Symfoclipse includes two plugins: * The Symfoclipse core plugin, a plugin that enables Symfony's command line actions from within Eclipse. * Symfoclipse YAML editor, an editor and validator for the YAML format which is the main format used by Symfony for its configuration files.
Uml2symfony translates a argoUML uml file into symfony elements see : http://argouml.tigris.org/
]]>