Linked by Eugenia Loli on Thu 8th Sep 2005 16:53 UTC
Gnome The Gnome Project released version 2.12 yesterday. We had a quick look at it by using the latest Gnome Live CD (1.12-pre) and Foresight 0.9.0 (2.12 final) and here are our thoughts over 2.12 and Gnome's status in general.
Thread beginning with comment 28864
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Agreed Docs Suck!
by on Fri 9th Sep 2005 08:55 UTC in reply to "Agreed Docs Suck!"

Member since:

I have to agree with one thing. GNOME documentation sucks! Developer docs that is

I agree too, though they are improving, as they are more and more auto-generated.
Still, the problem is that tutorials and howtos are not maintained. They still are usable because Gnome has backward compatibility until 2.0, but if you remove all deprecated symbols, nearly all the docs are obsolete (except API reference docs).

But it took me days to figure out how asynchronous operations actually works with gnomevfs

Look, I'm no genius, I'm not even programming regularly, but I found in, say 5 minutes, a recent example on how to do that (and I was not even searching for that).

Days to figure out how gconf actually works

It took me minutes ... I found all the docs I needed. I'm trying to updating some of my old Gnome apps (that still works, but they are Gtk 2.0 apps) and so, I started learning recent Gnome and KDE. The most difficulties I had till now, is avoiding all the deprecated stuff, and I still could use GConf in less than an hour.

Do I need to restart gconf after installing schema files?

Have nothing to do with programming, but no you don't.

And I still have no bloody clue how to, when to, and if to use most of the libgnome libraries

Had nearly no problem with that. The only problem I had is that all these are marked deprecated (in the docs, not in the code), but most still have no equivalent. When equivalents are available, it's written in the docs.

Hacking on GNOME is no fun. It's tedious and you spend weeks just figuring out how things should work. When they do work though, it rocks.

I disagree, I have a lot of fun hacking on Gnome. At start, I agree that it is more tedious than it should, a book on Gnome 2.12+ development is long overdue. But once you grasped how it works, you develop pretty fast with it. I'm still in the discovering phase, and I've not used GnomeVFS yet (seems to be the hardest part), so perhaps I will change my mind soon. But even as I saw why GnomeApp is a mess and why most of libgnome{,ui} need to go, it's not difficult to grasp. My secret is that I use the DISABLE_DEPRECATED flags, so I catch every obsolete code very fast.

With respect to RAD. Use Python, PyGTK, GNOME Python and Gazpacho. That's all you'll ever need for RAD. Anyway good review overall.

Well, I still dislike python, because to this day, Gnome python apps still have memory leaks (I use mostly bittorrent) though it's improving. Anyway, in my way back to Gnome and KDE devs, I'm starting with emacs/vi for Gnome, will be continuing with Anjuta (which I like very much, but I removed old Anjuta 1, and Anjuta 2 is still to buggy to even start a project, perhaps I will be able to help once I master more of Gnome 2.1x dev) for Gnomemm and finally, will use KDevelop when I will be on to KDE dev.

Reply Parent Score: 0

RE[2]: Agreed Docs Suck!
by on Fri 9th Sep 2005 11:01 in reply to "RE: Agreed Docs Suck!"
Member since:

>> Do I need to restart gconf after installing schema files?

> Have nothing to do with programming, but no you don't.

Actually you do have to restart gconfd or new schema files will not be picked up.

gconftool-2 --shutdown

or just kill the process. Failing to do so will mean apps will not get the default values specified when they read the keys.

Reply Parent Score: 0

RE[3]: Agreed Docs Suck!
by on Fri 9th Sep 2005 12:36 in reply to "RE[2]: Agreed Docs Suck!"
Member since:

Actually you do have to restart gconfd or new schema files will not be picked up

You can explicitely load them in your app though, that's what I planned to do anyway, at initialisation.

gconftool-2 --shutdown or just kill the process. Failing to do so will mean apps will not get the default values specified when they read the keys

That should be a bug ... Perhaps related to the cache. I suppose that's one big architectural problem of GConf if it can't be fixed. Now, with latest kernel using inotify, and latest GConf using it too if it is available in kernel, I suppose this can be overcome.

Reply Parent Score: 0