Re: [glade--] Current development?

Hi Dan,

Sorry, you hit my summer holidays and a rather busy time at work. On the 
other hand it took me four times (different days) reading your post to 
get a concrete idea what you really intend. So it took rather long to 
answer. Sorry.

Dan Lyke schrieb:
> So I was going along fairly smoothly using glade-2 and glademm with
> some diff and patch scripts that I'd hacked together, but at some
> point things broke, probably when I came up against a couple of
> current controls that aren't supported in glademm.

Sounds like gnome controls (yes they are hardly supported, but you can 
always fall back to --libglade) or brand new glade-2 features.

> 
> something that can run multiple times and it'll either set up a
> skeleton project or do its best attempt at updating the source code to
> keep up with recent changes.

Since meddling with user editable C++ files (and I sometimes like to 
spread different signal implementations across several .cc files) is far 
from trivial to do correctly I decided to stay away (and users did not 
insist on adding it).

If I get you right, you want to insert the signal callback skeletons 
from foo_glade.hh into foo.hh and foo.cc. I would recommend to take that 
road since getting the correct return value and argument type is 
difficult to automate with gtkmm (you might parse the gen_h or gtkmm/*.h 
files).

> I started to hack together something similar, but C++ is more complex
> than Perl and gtkmm is more complex than gtk2-perl, and I realized
> that this was more than an hour's worth of hacking.
> 
> So should I continue with my development efforts (I'm about to grep
> the gtkmm include files for signal names so I can figure out the right
> calling parameters for each of 'em) or is there something else I
> should glom onto? I've got the glademm source code, but it's... not
> immediately obvious where to start hacking, and C++ seems like the
> wrong language to be doing this in anyway.

I decided to copy the parameters by hand from the .h files to 
writers/*.cc [there are not so many signals out there]. Both ways 
(extract the information from foo_glade.hh or from gtkmm/*.h) seem 
equivalent (though the foo_glade.hh syntax should be less complex).

    Christof

_______________________________________________
glademm-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/glademm-list

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFBUE27ng+R+0ucfO0RAsWPAJ93cPXm+E2S6vsKsYw8rDJDkvXJTgCgohmv
xI7oRItHD0G+UXuFL6ti7dU=
=dsNo
-----END PGP SIGNATURE-----