Comments on: Killing libgnome/ui http://blogs.gnome.org/rodrigo/2006/07/03/killing-libgnomeui/ From lost to the river Tue, 24 Nov 2009 22:48:55 +0100 http://wordpress.org/?v=2.8.6 hourly 1 By: Martin-Éric http://blogs.gnome.org/rodrigo/2006/07/03/killing-libgnomeui/comment-page-1/#comment-341 Martin-Éric Tue, 30 Nov 1999 00:00:00 +0000 http://blogs.gnome.org/rodrigo/2006/07/03/killing-libgnomeui/#comment-341 One level of separation I would like to see is between GTK and GNOME-specific libraries. This would make it a LOT easier to build lightweight, GTK-only versions of popular applications, simply by configuring out GNOME libraries at compilation time. <p/>One example of where this would be useful is with Xubuntu's evince-gtk. The amount of patching required to get Evince to build without GNOME stuff seems a bit ridiculous. This sort of diet version is exactly what's expected for embeded devices and for GTK-based lightweight desktop environments. <p/>Making it easier to scale DOWN applications, simply by skipping the all-in-one libgnomekitchensink you are talking about at configure time would be an extremely desirable feature. It would also simplify the life of those making embeded systems or assembling lightweight applications sets for desktop environmnets that don't extend above the GTK layer. One level of separation I would like to see is between GTK and GNOME-specific libraries. This would make it a LOT easier to build lightweight, GTK-only versions of popular applications, simply by configuring out GNOME libraries at compilation time.

One example of where this would be useful is with Xubuntu’s evince-gtk. The amount of patching required to get Evince to build without GNOME stuff seems a bit ridiculous. This sort of diet version is exactly what’s expected for embeded devices and for GTK-based lightweight desktop environments.

Making it easier to scale DOWN applications, simply by skipping the all-in-one libgnomekitchensink you are talking about at configure time would be an extremely desirable feature. It would also simplify the life of those making embeded systems or assembling lightweight applications sets for desktop environmnets that don’t extend above the GTK layer.

]]> By: meek http://blogs.gnome.org/rodrigo/2006/07/03/killing-libgnomeui/comment-page-1/#comment-342 meek Tue, 30 Nov 1999 00:00:00 +0000 http://blogs.gnome.org/rodrigo/2006/07/03/killing-libgnomeui/#comment-342 We also need libgnome/ui for remote dialog authentication. We also need libgnome/ui for remote dialog authentication.

]]> By: Ludovic Danigo http://blogs.gnome.org/rodrigo/2006/07/03/killing-libgnomeui/comment-page-1/#comment-343 Ludovic Danigo Tue, 30 Nov 1999 00:00:00 +0000 http://blogs.gnome.org/rodrigo/2006/07/03/killing-libgnomeui/#comment-343 IMHO, yes, a library for desktop-related things would be nice but I would advise it NOT be the libgnome/ui. It could happen in another lib that would be renamed, once and only once current libgnome/ui had been killed. Clean, safer and with more visibility. IMHO, yes, a library for desktop-related things would be nice but I would advise it NOT be the libgnome/ui. It could happen in another lib that would be renamed, once and only once current libgnome/ui had been killed. Clean, safer and with more visibility.

]]>