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!
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
So, we had a cron job hanging for hours. No idea why. So, I started debugging. It all came down to a call to in_array().
]]>
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.
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.
t is something that I had to think about in my day job, because my team is migrating to PHP for web development and I believe that we simply do not have enough time for them to learn JavaScript’s intricacies, I needed to be the one person who would have to wrestle JavaScript when problems happened. I therefore needed a way to insulate them from the gory details, which is why I created ExtPHP. As you may have guessed from subtle hints, such as this entry’s 12-feet tall header, ExtPHP creates a PHP wrapper for ExtJS
]]>
phpUnderControl is an addon application for the continuous integration tool CruiseControl, which integrates some of the best PHP development tools. This project aims to make your first steps with CruiseControl and PHP as easy as possible. Therefore phpUnderControl comes with a command line tool that performs all modifications to an existing CruiseControl installation.
Rares sont les personnes qui connaissent la fonction register_shutdown_function, et pourtant, elle est très utile. http://fr2.php.net/register_shutdown_function Elle permet de réaliser des traitements hors transaction HTTP.
To put it simply, Krumo is a replacement for print_r() and var_dump(). By definition Krumo is a debugging tool (PHP4/PHP5), which displays structured information about any PHP variable.
The day is nearly upon us! Drupal 7 will open up developers to PHP 5 functionality when it is released next year. Already, there is talk of how, and if, to leverage PHP 5's object handling now that we don't need to deal with the weirdness of PHP 4's object model. Of course, because it's Drupal, our army of performance czars want to know just what the cost is for object handling, and especially advanced object magic like __get(), __call(), the ArrayAccess interface, and so forth.
PHP 5 propose désormais une alternative crédible à .NET et J2EE. Les entreprises qui l'utilisent, en parallèle de technologies concurrentes, apprécient sa simplicité et sa souplesse. L'apparition d'outils de développement favorise l'adoption du langage pour des projets critiques.
PDO_INFORMIX est un pilote qui implémente l'interface de PHP Data Objects (PDO) pour autoriser l'accès à PHP aux bases de données Informix.
Alors que tout semble laisser croire que nous sommes dans l'année de la montée en puissance du .NET, il n'en reste pas moins que de nombreuses sociétés et de nombreux projets sont et se construisent dans des technologies autres telles que le PHP. Tentons ainsi de mieux comprendre, au travers de cet article, les méthodologies de communication entre ces deux mondes.
You will probably need to reuse a piece of code that you developed for one of your symfony applications. If you can package this piece of code into a single class, no problem: Drop the class in one of the lib/ folders of another application and the autoloader will take care of the rest. But if the code is spread across more than one file, such as a complete new theme for the administration generator or a combination of JavaScript files and helpers to automate your favorite visual effect, just copying the files is not the best solution
]]>
PHP 5.2.0 wins out on 3 out of 10 test. Particularly the reading of GLOBALS is faster. PHP 5.1.6 wins on 6 test though.
]]>
Interactions on the client side, complex visual effects or asynchronous communication are common in web 2.0 applications. All that require JavaScript, but coding it by hand is often cumbersome and long to debug. Fortunately, symfony automates many of the common uses of JavaScript in the templates.
]]>
]]>