ConFoo 2012
27 Feb - 3 Mar 2012 at Hilton Montreal Bonaventure Hotel

Excellent présentation des outils.

J'espère que les slides seront disponibles, ou du moins la liste des outils, pour pouvoir y faire référence et recherche un outil plus en détail.

Ghislain

Also if you see this Simon, please let me know what kind of research I could have done to augment my talk, as I would like to investigate anything relevant that I missed. I tried to research everything I could find that was in the same field, both when I myself was trying to find a way to DRY my CSS and later when I was preparing the talk.

As a reply to those who feel I didn't explain how OOCSS and DRY are compatible, the idea I was trying to get across was that OOCSS and DRY are not the same type of thing, and that all the properties of OOCSS other than how you get it onto your HTML are compatible.

DRY just offers a way to organize your selectors and avoid duplicating properties, similar to mixins in LESS/SASS, so it is in fact a replacement for those technologies.

On the other hand, OOCSS (and SMACSS, which is probably even better) are systems for deciding on groups/names that define your style. If you want to use OOCSS or SMACSS then you can still use DRY, just use the other system to decide what your DRY Groups will be, and use DRY to think about/implement the groups.

Those systems often encourage you to instead add non-semantic classes into your HTML, which is not how CSS classes are supposed to be used. In that sense my system DOES contradict OOCSS, but IMHO only in the least important way. No one would say that using OOCSS with LESS "contradicts" it, it's just another way to organize your selectors, it's the same with DRY! If you don't care about using CSS in the way it was meant to be used (style separate from content) then that's fine, you can do whatever you want. My system is intended for people who see the benefits of style/content separation and want an elegant, standards-based solution.

Le code est disponible sur son compte github : https://github.com/testinfected

C'est certain que quelqu'un qui ne connaît pas la syntaxe de JQuery ou JavaScript peut être perdu par cette présentation car il y avait beaucoup d'éléments dans les exemples de code. Il aurait peut-être fallu avoir moins de code et l'expliquer plus en profondeur.

Cela dit, la présentation était bien structurée.

Loved the talk. It's always good when you can work alongside the speaker and try out things from the talk. Good humour, well paced.

Thanks for the feedback folks, it helps.

Got into this talk late, but got some good info out of it. Don't think there's anything I can tell the speaker to help him improve, he's already there.

Vincent connaît parfaitement sa matière et est un bon orateur. La présentation était toute aussi intéressante!

Pour ceux qui voudraient le code de sa présentation, c'est dans son github: https://github.com/testinfected

Must agree, was a good conference. It was clear, good example.
The only con was the room, when you sit back there, you might not see the slides.

The speaker was clear.