In the last article in the June issue of we discussed the development environment—the Netbeans IDE, the Symfony framework and the XAMPP Web server. In this article, let us learn more about Symfony application development, which includes the Symfony framew

LINUX For You,

Symfony is based on the MsC architecture, with special emphasis on the abstraction of various layers. This reduces dependency among the different components. For example, at any point during development, you can change your database engine, or the HTML view of your application, with negligible impact on the schedule. We will see how this is possible.

Symfony uses an OoM (Object oelationship Mapper) and a database abstraction layer to segregate the database layer from the application layer. The OoM maps classes to database tables; queries are sent to the database via the OoM. Currently, Symfony supports two OoMs—Doctrine and Propel. WhH YLHw-UHODWHd fiOHV Ln WhH ‘templates’ folder. Then there is the ‘web’ folder, which holds all the CSS, gavaScript and images. For example, if the people module has a search function, then WhH FRdH IRU VHDUFh wLOO EH DddHd WR WhH fiOH ‘actions.class. php’ ; and the result of the function will be displayed with the template ‘searchSuccess.php’, which will be decorated with the ‘layout.php’ fiOH.