Re: [Gtk2hs-users] --disable-deprecated & stuff that remains to be bound

[Duncan C. <dun...@wo...>]

On Wed, 2004-08-04 at 10:08, Axel Simon wrote:
> > I was thinking of adding a --disable-deprecated option to ./configure to
> > indicate that we don't want to generate bindings for any deprecated gtk
> > functions.
> 
> I think we can always supply that flag since we only want Gtk 2.X functons.

There's stuff that has become deprecated since 2.x. Eg the GtkCombo has
been superseded by GtkComboBox. There are 9 classes in hierarchy.list
that are deprecated. The GtkToolbar got a major change in interface in
2.4, we now bind both old and new, so on gtk-2.2 systems you only get
the old deprecated interface.

> Where are we using deprecated functions? I'd rather we don't at all.

There's really only a handful. It's mostly in the Combo & Toolbar
bindings, but there's some miscellaneous ones elsewhere. We'd find them
soon enough by enabling --disable-deprecated.

> So 2.2 compiles for you? I have to check my symbol problem. Your statistics 
> look good, though. More than 1000 functions!

No, I'm still building against 2.4, I'm just comparing coverage vs 2.2.

> >      70 gtk_widget
> Here is a lot of useless stuff I think.

Yes, I've cut it down to 40ish without binding anything extra so far.
:-)

> Possibly. Don't they use the Atoms to specify what the data is you're putting 
> into the clipboard? That is definitely needed, i.e. if you're writing an 
> application that has it's own internal data structures you can cut and paste.

Actually looking again, your right, there's only two functions where the
clipboard to use is determined by a giving an Atom. Atoms are also used
for some of the metadata when sending & receiving. We could probably
present an interface with Strings that does not expose the GdkAtoms,
it'd have to convert the strings to Atoms.

Duncan