My FOSDEM “design patterns in GObject” talk

I got a little bit sick this weekend. Nevertheless managed to do my presentation at FOSDEM. I decided to stay in bed on Sunday, which is why I wasn’t at FOSDEM yesterday. Sorry if you wanted to talk to me and hoped to catch me on Sunday.

I was a little bit afraid a lot people where going to tell me how much they dislike the “buzzword” “design pattern”. I guess I shouldn’t have been afraid as i.m.h.o. a lot people where interested in my talk and a lot (interesting) questions where asked. Regretfully I was a little bit sick so I might have been answering those questions like an uninterested asshole. Sorry if that was the case. And I hope I didn’t make somebody else in the GNOME room sick.

If I did (I had stomach flu), visit GUADEC at Spain this year, I’ll buy you some free beer at the meeting. Don’t worry about me, I feel a lot better today.

I’ll put the slides online soon. You can find the samples here, here and here.

5 thoughts on “My FOSDEM “design patterns in GObject” talk”

  1. I don’t know about other people, but to me design patterns aren’t hyped or anything.
    I even bought the book you recomended in your talk. (good stuff, as far as i’ve read so far)

    I now see where you got quite a bit of your inspiration from ;)

    And if Design patterns are so new that they should be thought of as buzz words, then those people should probebly learn from history and read “Real Programmers Don’t Use Pascal”
    http://www.pbm.com/~lindahl/real.programmers.html

  2. your talk was indeed very good. I’ve been using interfaces with gobjects for a while, and the approach is much more cleaner than just using abstract classes and signal closures to relay the methods to the implementations. also, the fact that the methods of GTypeInterface objects can have actual implementations instead of being “virtual” makes them much more useful.

  3. I hope you like the rest of the book too, stratos. But I know you will. And, indeed, the book is (and was) a source of inspiration for me.

    Hey ebassi. Nevertheless, I don’t recommend putting implementations in those methods, as a typical OO programmer will not expect implementations in an interface type.

  4. pvanhoof: as the GTypeInterface objects allows implementation, I like to compare them to “traits” (or roles) more than interfaces in the java acception. I think they are more powerful a tool than the average interface used in object oriented design.

Comments are closed.