Unfortunately the Symfony documentation does not provide any details on how to configure Assetic to use LESS. There is a blog post by Dustin Dobervich that gives some pointers, but after following the instructions, Assetic issued the following error: Cannot find module 'less'. We searched around without much success. After several tries, we nailed the configuration.

It's an easy two-step process: first you be sure you have "npm" (the package manager) installed on your system, then you modify your Symfony app.yml file to point to the Node modules path.

After having had a look at Silex, and struggling with the somewhat cumbersome ini configurations and YADIF, I wanted to try out whether I could use Pimple as DI container for ZF 1.x Turns out I can, as you can just select Pimple to be the bootstrap container.

Hsi example (gist of the code here) also shows how to subclass the container and add in some default settings objects into the container. Pimple is a small, lightweight dependency injection container from Fabien Potencier of the Symfony framework.

Following on from the discussion on modules, we can hook into the event system to do module specific bootstrapping. By this, I mean, if you have some code that you want to run only if the action to be called is within this module, you can hook into the Application's dispatch event to achieve this.

He starts with an example of a basic module (Simple/Module.php) and shows how to define an "onBootstrap" method that calls the "onDispatch" method (when hooked to the event manager) to do some module-specific bootstrap operations. The RouteMatch feature is used to ensure that you're in the right controller/namespace combo to use the module.

I don't know about you, but for me building HTML Forms and styling HTML Forms are maybe the most boring things in web development. It's repetitive and takes a lot of time to do things correctly. That's why tools like Twitter's Bootstrap and PEAR's HTML_QuickForm2 can help with this part of our job. Wouldn't it be nice to have QuickForm2 generate a markup compatible with Bootstrap CSS, so that you could get a nice looking form without to much efforts? Well, that's what I plan to do here.

He starts by creating a simple QuickForm2 form with no renderers attached (no pre-defined styles) and a custom render callback that wraps the items in "div" tags with the correct styles. There's also a custom renderer included for grouping items with additional styling attached.

In a follow up to my popular post on Symfony2, the open source PHP framework we use at OpenSky, I'm providing an easy guide to getting started using Symfony2. This isn't your basic "Hello World", but a practical guide to beginning a project with Symfony2.

He walks you through bootstrapping a sample application, applying a fix those on OSX might need and creating the application using the symfony command line tool to build everything you'll need.

His talk introduces you to bootstrapping, shows how to get started with Zend_Tool and shares code and configuration details for using resources in your controllers.

You can listen to this latest episode either through the in-page player, by downloading the mp3 or by subscribing to one of their feeds. The slides are also on Slideshare if you'd like to follow along.

Let's say that you want to use your own view object within your Zend Framework application. Creating the view object is easy enough in library/App/View.php along with adding the App_ namespace to the the autoloader in application.ini. All we need to now is get Zend_Application to bootstrap with our new view class. There are two ways of doing this: within Bootstrap.php or using a custom resource.

He includes the code to make it happen both ways - by adding an _initView method in the application's Bootstrap.php file or by creating a new class called App_Resource_View that overrides the getView() method that grabs the custom object.

Using Zend Framework as an MVC application is probably the most common usage examples for Zend Framework. When you create such an MVC application, you will probably have heard about modules: reusable components of your application. [...] In my case, I usually just copy and paste the module from one base project into a new project. That's easy. But it would be cooler to package your module as a Phar file, and run that file instead.

He includes the code that can be dropped into your Zend Framework installation - MyLib_Application_Resource_Modules - that handles the bootstrapping of the phar files and executes the Boostrap.php file that it finds inside. He also points to this other article from Cal Evans about working with phar files in the Zend Framework.

I was trying to load a Front Controller plugin which resides in app/modules/my_module/controllers/plugins/ and not in the '�usual'� lib/My_App/Plugin/. I want this plugin to be called in every request and I want the plugin file to be under it's '�parent'� module.

To solve the problem he added a path to the Zend_Application_Module_Autoloader as a resource and registered it in the front controller. He includes some code to show how it works - a simple bootstrap with two _init functions, one for the news autoloading and another for plugins.

In Zend Framework 1.8.0, we added Zend_Application, which is intended to (a) formalize the bootstrapping process, and (b) make it re-usable. One aspect of it was to allow bootstrapping of individual application modules -- which are discrete collections of controllers, views, and models.

He talks briefly about why module boostraps are run on every request (getting into some detail on Zend_Application), how you can properly set up your boostrapping process and how you can use plugins to initialize only the things you might need and, as he openly admits, that there's just not a really good way to handle this sort of module funcionality.