Re: GnomeVFS backend for GtkFileChooser
- From: Owen Taylor <otaylor redhat com>
- To: Alexander Larsson <alexl redhat com>
- Cc: Havoc Pennington <hp redhat com>, Jeff Waugh <jdub perkypants org>, "desktop-devel-list gnome org" <desktop-devel-list gnome org>
- Subject: Re: GnomeVFS backend for GtkFileChooser
- Date: Thu, 30 Oct 2003 09:48:10 -0500
On Thu, 2003-10-30 at 09:26, Alexander Larsson wrote:
> > The foo/fooui library splits were done to allow apps to avoid relying on
> > an X connection, or linking to all the X/GTK+ libs if they aren't GUI
> > apps. But what we're talking about here has nothing to do with that.
> > It's simply an issue of the build graph. And there are no requirements
> > on the build graph other than "no cycles"
>
> Really? How do you implement an interface without linking to the
> library?
>
> In particular, how would you call:
> g_type_add_interface_static (file_system_gnome_vfs_type,
> GTK_TYPE_FILE_SYSTEM,
> &file_system_info);
>
> without linking to the library that defines gtk_file_system_get_type().
>
> You can't. So, either:
> a) gtk_file_system_get_type() goes in some lib below gtk+
> b) gnome-vfs links to gtk+
> c) the gnome-vfs implemenation of GtkFileSystem goes in libgnomeui
>
> pick your poison.
>
> Personally, I favour c.
gnome-vfs just builds a separate module and drops it into place; a
different shared object.
Regards,
Owen
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]