By Romain Dorgueil on Monday, April 6 2009, 23:48 - release
After a long alpha development stage, I released this morning the first BETA version of sfDynamicsPlugin. But... You may wonder, what is that?
sfDynamicsPlugin is a flexible assets manager for symfony which can be used to manage javascript libraries and their associated stylesheets. It supports packing, and CSS minifying, while keeping the full readable source in development environment.
By Romain Dorgueil on Thursday, March 12 2009, 13:34 - discussion
public function executeBarfoo(sfWebRequest $request)
{
return $this->renderComponent('my_module', 'my_component', array());
}This is an attempt to take over the first place on google for the query how to render component action symfony.
By Romain Dorgueil on Thursday, July 10 2008, 23:55 - database
Any modern relational database engine supports the onDelete and onUpdate attributes on foreign keys. Propel and Doctrine of course allows to define it in the schema file (yaml or xml) and I believe it is important to explicitly set it.
By Romain Dorgueil on Tuesday, July 1 2008, 23:52 - release
The longly awaited 1.1 version is finally out after long months of development. After doing this, Fabien started the 1.2 branch, and you can take a look at that magnificient revision which for sure opens a new era of symfony developments.
By Romain Dorgueil on Monday, June 16 2008, 23:55 - discussion
After more than one year since symfony 1.0 was released, symfony 1.1 goes more and more mature each day. Recent RC releases are a proof of it, but many people are still concerned about whether or not they should migrate.
By Romain Dorgueil on Wednesday, April 30 2008, 23:56 - how-to
As you may now by now, Symfony 1.1 introduces a new powerfull event dispatcher inspired by Apple Cocoa's NotificationCenter. Basically, it allows any entity to "listen" to events, and get a call on the registered callback if this event ever happens.
Symfony 1.1 provides some default events you can listen to, but of course you can create your own events if you need.
To listen to an event, you need to use the "connect" method on the event dispatcher instance. The first parameter is the event name, and the second is a PHP callable that will get called if the event happens.
$dispatcher->connect('user.change_culture', array($this, 'listenToChangeCultureEvent'));To use the dispatcher for your own needs, you just need to define your event name in your project specifications, and send notifications to it. Depending on the behaviour needed, three options are offered:
The simpliest way is to notify all listeners with the ->notify method.
$dispatcher->notify(new sfEvent($this, 'my.super.cool.event'));Sometimes, you prefer to notify all listeners until one says "Ok guys, I handled this one. Don't worry about it anymore".
$dispatcher->notifyUntil(new sfEvent($this, 'my.super.cool.event'));The first listener that will return non-false value will stop the event chain.
The last notifying method is called filtering. You set this up when you want to permit anything to act as a filter on something, meaning any listener can modify a source object.
$dispatcher->filter(new sfEvent($this, 'my.super.cool.event'), $objectToFilter);Every listener must return the filtered value (or the original object if nothing was done) to pass to the next listener.
One of the first practical applications that came to me was the new way of registering routes in plugins. In symfony 1.0, a coincidence made possible to use the routing in a plugin's config.php but that's not possible anymore in symfony 1.1, so you have to use the event dispatcher. To accomplish this, we're going to set up a routing.load_configuration listener in the plugin's config.php:
$this->dispatcher->connect('routing.load_configuration', array('myPluginRouting', 'listenToRoutingLoadConfigurationEvent'));Then you just need to create the callback class/method:
class myPluginRouting
{
/**
* Listens to the routing.load_configuration event.
*
* @param sfEvent An sfEvent instance
*/
static public function listenToRoutingLoadConfigurationEvent(sfEvent $event)
{
$r = $event->getSubject();
// preprend our routes
$r->prependRoute('my_route', '/my_plugin/:action', array('module' => 'myPluginAdministrationInterface'));
}
}Here we go :-D
« previous entries - page 1 of 4
© Copyright 2007-2008 daKrazy. All rights reserved.
Design and template by hartym
Last comments