It finally got out the door last night after some headaches trying to get it to compile cleanly both with and without gob installed. It is feature complete and pretty much what I wanted for 2.10. Same GNOME doesn’t have all the new toys I had wanted to put in the rewrite, but time has been short recently so I concentrated on getting the core code right. It is still better than the original.
Another missing feature is the new high scores dialog. I have rewritten it as a generic widget (it was Mines specific in 2.8) and I have used it in Same GNOME and Mines, but I never got the time to convert the other programs. So it is there, just not universal.
I was going to dedicate this week to bug fixing. I will get a little done, but between the last of the feature coding and my impending wedding not a lot more will be done. Next week is going to be the honeymoon, and I won’t be paying any attention what-so-ever to GNOME.
gob
I have promised myslef for a long time to use more automated tools for coding that doesn’t require much creativity. Lets face it, because of C’s constraints, writing GTK code, and especially widgets, can be ridiculously slow due to all the long names and the object orientation internals that C can’t hide. So, when I came to write the new high scores widget, I decided to use gob. The reasons were straight-forward: I needed to get the widget written quickly and I can never remember all the stuff you need to do to get a GTK widget written properly. Gob handled the boring details for me and provided a nicer syntax for some of the object-oriented stuff.
I am a little worried that gob has been around for a long time now and doesn’t seem to be widely used (at least not in what I have checked out of GNOME CVS). This suggests there is some bad point I haven’t noticed yet.
You don’t need gob to compile gnome-games, you only need it if you want to work on the high scores widget.