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.
Symfony 1.1 is out, and the winner is... 1.2!
By Romain Dorgueil on Tuesday, July 1 2008, 23:52 - release
Towards symfony 1.1
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.
Overview of symfony 1.1 event dispatcher
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.
Listen to an event
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'));Create a custom event
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:
Simple notifications
The simpliest way is to notify all listeners with the ->notify method.
$dispatcher->notify(new sfEvent($this, 'my.super.cool.event'));Notifications until something
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.
Filtering notifications
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.
Practical use: Register routes in your plugins
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
Don't be fooled by awkward view.yml js/css positionning syntax!
By Romain Dorgueil on Monday, April 21 2008, 23:55 - how-to
Short post today about advanced view.yml configuration (in symfony 1.0, and 1.1) for assets.
You can give additional options to "javascripts:" and "stylesheets:" sections, but the sin equa non condition is to know about the yet very un-documented view.yml assets syntax.
So here it is:
javascripts: [ jquery: { position: first } ]
stylesheets: [ mycss: { position: last, media: screen } ]
I don't know if there are others options like thoose available, but taken the 'position' attribute apart, which is extracted to become the $position method argument of sfWebResponse::addJavascript() and ::addStylesheet, any other option is passed in the $options array.
Methods prototypes below:
HashBin now available in open-source flavor
By Romain Dorgueil on Monday, March 17 2008, 23:58 - sites
Our first violin missed his plane yesterday, so Kwatuor is still not available in the upcoming unusable buggy pre-alpha (that miss all the functionalities anyway).
But while we're waiting for him to be available, I released HashBin in open-source, so anybody can dive into the code, and help me making it evolve. It still needs many attention, but hey, time is not the most available resource I have, and that's one of the two major reasons to give it to the community. Another one is that there is not so much open source symfony applications, and even less open source doctrine applications. After the doctrine 1.0 feature-freeze announcement, this could be a step to have simple sample applications (I hear little sarcastic laughs in the background...) people could dive in to learn this amazing ORM.
Well stop talking, here is the code.
- TRAC web interface: http://trac.dakrazy.net/
- SVN DAV repository: http://svn.dakrazy.net/hashbin/trunk/
SVN access is read-only for anyone, if you ever want to contribute, I'll be glad to grant you a commit access either on trunk or branch (still have to make up my mind, but at beginning that's not very important). Just ask me on IRC (hartym@freenode).
What amazing feature will you invent today?
I'd like to hear a Kwatuor play nice symfonic music
By Romain Dorgueil on Tuesday, February 26 2008, 23:58 - discussion
Today's post is a bit special.
This can be took as a question.
Or a call to developpers that have specific blogging needs.
Since quite a moment I used dotclear for blogging. That suit my needs, in some way, but maybe I'm more adaptating my needs to dotclear's capabilities. Maybe you're using wordpress. or any other. And I guess that must be the same for you, thinking for example of integrating one of those all-in-one blogging/cms platforms cleanly in another website, for example, is being more than utopian...
By clean I mean integrating it without having to duplicate the template. Neither having to use all functionalities if you only need a simple article list somewhere... And without being limited if you need to display the headers of those on another website...
I'd better not speak of blog networks communicating, or taking content from RSS/XML/anything feed in a flexible way.
So today I'd like to announce the birth of Kwatuor. Kwatuor is a blog platform project using symfony and doctrine, that will in the near future use doctrine migrations to get content from an existing dotclear/wordpress project, or any other source platform someone has enough need with he'd take the time to write migration classes for.
Templating system will be different. I'm still hesitating between a generator approach (generated partials from a dynamic skeleton, that all can be customizable) and a real proper template system (but still any part would be customizable). Only major difference with blogging platform would be the total forbidding of DRY-breaks a dotclear-like templating system is doing everyday. And this extends to integrated blogs, in wider projects.
In fact I started developing it for my own needs, but I think this is typically the kind of project everybody would need someday. Maybe you hate being jailed in your obscure, yet very good, but specific and... even more obscure blog platform.
So I'm wondering now, if people (you :p) would be interested in this project. If so, I'll make a public SVN/trac next week, so concerned users will be able to give feedback with code in their hands. Would this be usefull to you? Would you contribute to this open-source project? Do you have good (or bad :p) ideas about concepts to take in consideration from the beginning?
Related links
« previous entries - page 1 of 3
Last comments