Re: GnomeVFS backend for GtkFileChooser
- From: Alexander Larsson <alexl redhat com>
- To: Havoc Pennington <hp redhat com>
- Cc: Jeff Waugh <jdub perkypants org>, "desktop-devel-list gnome org" <desktop-devel-list gnome org>
- Subject: Re: GnomeVFS backend for GtkFileChooser
- Date: 30 Oct 2003 15:42:17 +0100
On Thu, 2003-10-30 at 15:26, Alexander Larsson wrote:
> On Thu, 2003-10-30 at 15:04, Havoc Pennington wrote:
> > On Thu, 2003-10-30 at 05:34, Jeff Waugh wrote:
> > > <quote who="Alexander Larsson">
> > >
> > > > > What do people think? Or does it make better sense to put this into
> > > > > libgnomeui [which is getting deprecated too fast for my taste, but...]
> > > >
> > > > Can't we put the GtkFileSystem interface in glib or something, then
> > > > gnome-vfs can have the implementation without depending on gtk+?
> > >
> > > (If that's doable, it would totally rock the casbah.)
> > >
> >
> > Why would we do this though, purely to rearrange the jhbuild build
> > graph? I don't see any other advantage. It doesn't make sense;
> > GtkFileSystem is the plugin API for GtkFileChooser, it has no other
> > purpose. So it logically belongs with GtkFileChooser. The
> > gnome-vfs-subclass of GtkFileSystem is a runtime drop-in plugin for
> > GtkFileChooser that enables gnome-vfs usage, so it logically belongs in
> > gnome-vfs or gtk+ as those are the two things it's related to. None of
> > this makes sense in GLib, as it's hugely GtkFileChooser-specific.
> >
> > Who gives a crap if you have to build gtk+ before gnome-vfs? In fact
> > "jhbuild list" shows that gtk+ already builds before gnome-vfs.
> >
> > 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.
Well, I guess you could make libgnomevfs-gtk instead of putting it in
libgnomeui. But what use is that? I guess it means apps can use the vfs
fileselector without linking to libbonoboui, but on the other hand its
another library slowing things down in the normal case.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Alexander Larsson Red Hat, Inc
alexl redhat com alla lysator liu se
He's a world-famous soccer-playing cop with a secret. She's a time-travelling
African-American research scientist who dreams of becoming Elvis. They fight
crime!
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]