Comments on: Zaragoza hackers meeting http://blogs.gnome.org/rodrigo/2005/09/19/zaragoza-hackers-meeting/ From lost to the river Sun, 23 Nov 2008 20:34:34 +0000 http://wordpress.org/?v=2.6.3 By: Mikkel Kamstrup Erlandsen http://blogs.gnome.org/rodrigo/2005/09/19/zaragoza-hackers-meeting/#comment-173 Mikkel Kamstrup Erlandsen Tue, 30 Nov 1999 00:00:00 +0000 http://blogs.gnome.org/rodrigo/2005/09/19/zaragoza-hackers-meeting/#comment-173 On the "Contributing to GNOME" subject, I have realised just lately what was blocking me from contributing (besides from the lack of time - but we all know that :-P). This is mainly concerning contributing code and to some extent documentation.<p/>Glib. Glib and especially the GObject system, are in fact quite non-trivial to grasp. There are excellent tutorials around for high-level GTK and the various language bindings, but none readily googlable on the inner workings of GTK and GNOME.<p/>Trying to work on something or just browsing through some code, it is quickly obvious that you'll need a good understanding of glib/gobjects to do non-trivial tasks.<p/>If all you know is Java, Python and C (like me) you'll be thoroughly confused the first time you look at the code behind a GNOME app. Writing a widget/gobject takes a whole lot more than writing a Java/Python object.<p/>With time I've come to understand the GObject system to some extent, but don't feel very comfortable with it. On the other hand it didn't take me more than a day to start playing around with QT4 and feeling quite comfortable - even though I've never really digged C++<p/>Well... Didn't know where to post this rant, I just came to think of it when I saw your blog. <p/>Cheers<br/>Mikkel On the “Contributing to GNOME” subject, I have realised just lately what was blocking me from contributing (besides from the lack of time - but we all know that :-P). This is mainly concerning contributing code and to some extent documentation.

Glib. Glib and especially the GObject system, are in fact quite non-trivial to grasp. There are excellent tutorials around for high-level GTK and the various language bindings, but none readily googlable on the inner workings of GTK and GNOME.

Trying to work on something or just browsing through some code, it is quickly obvious that you’ll need a good understanding of glib/gobjects to do non-trivial tasks.

If all you know is Java, Python and C (like me) you’ll be thoroughly confused the first time you look at the code behind a GNOME app. Writing a widget/gobject takes a whole lot more than writing a Java/Python object.

With time I’ve come to understand the GObject system to some extent, but don’t feel very comfortable with it. On the other hand it didn’t take me more than a day to start playing around with QT4 and feeling quite comfortable - even though I’ve never really digged C++

Well… Didn’t know where to post this rant, I just came to think of it when I saw your blog.

Cheers
Mikkel

]]> By: Rodrigo Moya http://blogs.gnome.org/rodrigo/2005/09/19/zaragoza-hackers-meeting/#comment-174 Rodrigo Moya Tue, 30 Nov 1999 00:00:00 +0000 http://blogs.gnome.org/rodrigo/2005/09/19/zaragoza-hackers-meeting/#comment-174 Well, the purpose of these meetings is to get people to hack on high level bugs, fixing apps, applets, etc, rather than working on library code. So, there is really no need to have them know about the inner workings of glib/gtk.<p/>Of course, what is needed indeed is to have those people all know GTK/GNOME programming a bit before coming to the meeting. Well, the purpose of these meetings is to get people to hack on high level bugs, fixing apps, applets, etc, rather than working on library code. So, there is really no need to have them know about the inner workings of glib/gtk.

Of course, what is needed indeed is to have those people all know GTK/GNOME programming a bit before coming to the meeting.

]]>