Re: gnome-vfs API freeze items
- From: Maciej Stachowiak <mjs noisehavoc org>
- To: Jonathan Blandford <jrb redhat com>
- Cc: Maciej Stachowiak <mjs noisehavoc org>, gnome-vfs ximian com, gnome-2-0-list gnome org
- Subject: Re: gnome-vfs API freeze items
- Date: Sat, 1 Sep 2001 16:59:00 -0700
On 01Sep2001 07:43PM (-0400), Jonathan Blandford wrote:
> Maciej Stachowiak <mjs noisehavoc org> writes:
> > On 01Sep2001 12:57PM (-0400), Jonathan Blandford wrote:
> > > Maciej Stachowiak <mjs noisehavoc org> writes:
> > >
> > > > * 8516 - [API] GClosure-ize everything
> > > > Note: I'm told this is critical for binding authors but I don't
> > > > really know the details of what it is, how to do it, or how much
> > > > work it would be.
> > >
> > > This actually needs to happen to all libraries in GNOME. I think it
> > > would be good to have an API review to see if any API's are
> > > inappropriate for LBs.
> > Has it been done for libgnome* yet? Also, can you point me to
> > information on how (and why) to do this?
> We need to write this up sometime. At a minimum, you need sure that
> every time you set user_data, you have a GtkDestroyNotify. Ie, you have:
> gtk_foo_set_func (), you need to do:
> void gtk_foo_set_func (GtkFoo *foo,
> GFooFunc func,
> gpointer data,
> GtkDestroyNotify destroy);
> Later on, you need to do (destroy) (data); in your "foo::destroy"
gnome-vfs is not GObject-based. Mostly it sets one-shot callbacks. One
exception is auth callbacks and I think there is a destroy-notify
there, but not a GtkDestroyNotify since it doesn't depend on Gtk+.
] [Thread Prev