Mirmo Dynamics

Bon voilà, j'ai décidé de prendre en main mon alimentation, et vu qu'il parait que le petit déjeuner est le repas le plus important de la journée, je commence par lui. Dans cette optique, j'ai acheté des pancakes de chez Pasquier. Je ne suis pas un expert en pancakes (mes deux seuls points de comparaisons sont des pancakes qu'on m'a fait quand j'étais au lycée et ceux de breakfast in america), mais franchement, ces pancakes sont une vaste plaisanterie. Ils sont vendus par dix, conditionnés dans des sachets fraicheur de deux pancakes chacun. La consistance de la chose est pour le moins décevante puisqu'au moindre mouvement un peu brusque, le pancake se disloque... Bon. Passé ce désappointement, on sort le sirop d'érable, et là, le drame se poursuit. Plus proche de l'éponge que du pancake, ce truc ne se rattrape même pas par son gout, qui, s'il n'est pas forcément mauvais, n'a rien a voir avec un pancake. Bref, à l'avenir, je cuisinerai mes pancakes moi même.

You have unsubscribed from "The Caribbean Weblog."

C'est con mais ça me rend un peu triste.

Just to say I packaged the 1.0.3 version of the zend framework on the phpmafia pear channel. It's a bit late I know, but at least it's here. Please note that I already have been notified of a problem regarding the Zend Locale's xml datafiles and that I hope to have worked out a solution for the next release (1.5 if all goes well).

Je voulais geeker un peu ce week end, et notamment travailler sur mon plugin "related by tags", mais malheureusement j'ai réactivé mon compte WoW. Autant dire que ma productivité globale est proche du zéro absolu. Mais je ne perds pas espoir, et je vais de ce pas inscrire quelques reminders bien sentis sur mon tableau blanc, et j'espère redresser la barre d'ici au jour de l'an.

It's a simple plugin (2 lines of code beside class and modules declarations) which allows routes created via the map.resources mechanism to be customized. Say you have the following map:

map.resources :members

It will generate routes like:

/members
/members/:id
/members/new

No say you want to i18n your app, in french for example, what do you do ? You just can't out of the box. This is where my plugin enters into action, just add a :route_name parameter to the map.resources call and you're set:

map.resources :members, :route_name => 'utilisateurs'

will generate routes like:

/utilisateurs
/utilisateurs/:id
/utilisateurs/new

It shall also work for nested resources, although I did not test that.

The code is actually pretty simple:

module ActionController
  module Resources
    class Resource
      def path
        route_name = @options.include?(:route_name) ? @options[:route_name] : @plural
        @path ||= "#{path_prefix}/#{route_name}"
      end 
    end 
  end 
end

To install just use script/plugin:

script/plugin install http://tools.assembla.com/svn/riskle/rails/plugins/named_resources

or to install as an svn:external resource:

script/plugin install -x http://tools.assembla.com/svn/riskle/rails/plugins/named_resources

Bon voilà j'ai craqué la semaine dernière, j'ai acheté une xbox 360. Donc si ça vous tente, et que vous en avez une également bien entendu, mon gamertag est ubermuda, n'hésitez pas à venir m'humilier sur skate, burnout revenge ou autre gears of war :-) J'en profite pour dire aussi que bioshock est vraiment un des meilleurs jeux auquel j'ai jamais joué.

Having started a few applications using the Zend Framework, I came out with a few practices that I tend to use over and over. In this post I'll quickly expose some of them and explain why I do things the way I do them. As you'll notice, most of them are already widely known and used over the ZF developer's community. Please remember that these practices are just what I do, and come with no garanty at all to be best practices.

Today I ran into an issue that I already ran into a few weeks ago when I did not have time to dig up, but today I had this time (this plus it's a really annoying issue as you'll see). The main symptom is that PDO does not throws exceptions when you'd expect it to. It's very annoying. The reason, in my case, seems to be that I am querying an old mysql (3.23.x in my case but any 4.x will do according to this bug report). I was not able to find any info from google, so I'm posting this here so that people know :-)

A PEAR package for the 1.0.2 version of the Zend Framework is now available from the PEAR PHPMafia channel. As usual, to install just issue the following:

pear channel-discover pear.phpmafia.net
pear install phpmafia/Zend

When anyone on #zftalk ask about where controller plugins should be kept, we usually responds something like have your own library namesapce alongside Zend/ and put it in it like YourNamespace/Controller/Plugin/YourPlugin.php. But what about application specific controllers ? There's a time where you have to write a plugin that relies on the application at such a level that using it elsewhere would make no sense. In that case, where can we store this plugin ? The question arised this morning, and we ended up to the fact that having a controller-level plugin directory would not hurt, after all. So one could have the following directory layout (simplified on purpose):

/application/modules/default
    /controllers
    /library/Plugin
        MyPlugin.php

The drawback is that in order to use autoload you would have to have each modules Plugin dir in the include path, which is a bit of a hassle. Instead, we could have the much more simple folloing layout:

/application
    library/Controller/Plugin
        MyPlugin.php

Which is simpler but does not allow for modules specific plugins. Anyway, the former layout would require a bit more logic in the bootstrap in order to extract every modules path as plugins are registered pre-dispatch.

Hope it helps with directory layout organization :-)

UPDATE

What I've finally decided to do is the following:

/application
    library/App/Controller/Plugin
        MyPlugin.php

So that application specific code gets prefixed with the App_ namespace.