Re: Proposed external dependency: libnotify
- From: "Christian Hammond" <chipx86 chipx86 com>
- To: "Sven Neumann" <sven gimp org>
- Cc: desktop-devel-list gnome org
- Subject: Re: Proposed external dependency: libnotify
- Date: Wed, 1 Aug 2007 00:51:22 -0700
Hi everyone.
Deja vu. I guess I'll give the usual response to this thread :)
I had a blog entry a while back addressing exactly why I didn't want projects to do this. libsexy is not libegg and I'm not wild about having to maintain two copies of the widget.
libsexy is at this point bundled on nearly every distribution shipping GNOME, to my knowledge. These distros are shipping notification-daemon and libnotify as well. It's pretty much a de facto standard at this point.
libsexy itself is used by a variety of GNOME applications now including Rhythmbox, gedit and xchat-gnome.
I would love to get libsexy's widgets bundled into GTK+, but that will require some extensions to widgets such as GtkEntry and GtkLabel to allow subclasses to better hook into the PangoLayouts of the widgets (by providing a signal indicating that the layout has been created and can now be modified). This would get rid of some of the hacks we have to use in libsexy, which would increase the chances of getting into GTK+. Any help would be appreciated here.
In the meantime, I'll ask the same question as I did before. Can we just consider libsexy or notification-daemon a blessed dependency given how widespread they both are these days? Or just allow libsexy and use that as motivation to getting GTK+ in shape to be able to include its widgets?
Christian
--
Christian Hammond -
chipx86 chipx86 comVMware, Inc.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]