Re: Please include into 2.22: libnotify, notification daemon

["Christian Hammond" <chipx86 chipx86 com>]

libsexy's widgets extends GTK+ widgets in uncommon ways. To get it integrated into GTK+ properly, someone needs to get new signals and API into GtkLabel, GtkEntry and some other widgets and then port these widgets over in a more sane manner. I would love to do it one of these days, but work and my personal life keeps me busy these days, and nobody else has volunteered to help out with this.

I would love to see these widgets in GTK+ as well. In the meantime, though, libsexy, like notification-daemon, is on practically every distro shipping GNOME and is in a lot of GNOME apps as well. So my argument applies to it.

I'm not saying let's put this into the desktop right now. I think it just makes sense to allow this to be an external dependency given how widespread it is.

Christian

On 9/28/07, Martin Meyer <elreydetodo gmail com> wrote:

Wasn't there a concern at one point about a libnotify dependency on
libsexy? I thought the discussion had mentioned getting some of the
libsexy widgets into gtk+, thus removing the dependency. Anyone else
remember that or am I just crazy?

/me goes off and searches...

Yes! Just last month!
http://mail.gnome.org/archives/desktop-devel-list/2007-August/msg00000.html
- the middle of a thread mentioning the dependency on libsexy. I would
*love* to see notification-daemon make it as an official part of the
desktop but what the libsexy dependency? Has there been any work on
resolving that?

- Martin

On 9/28/07, Murray Cumming <murrayc murrayc com> wrote:
> On Wed, 2007-09-26 at 02:07 -0700, Christian Hammond wrote:
> [snip]
> > notification-daemon and libnotify are on every distro shipping GNOME,
> > to my knowledge. Isn't it time to finally mark this as a blessed
> > dependency? More and more apps are using this and it's become a de
> > facto standard not only in GNOME but in practically anything not
> > KDE-based, GTK+ or otherwise. It's only doing harm by preventing it
> > from becoming a dependency, as it requires more work on the part of
> > the developers to develop, test and support conditional code.
>
> This seems sensible. Are there really no other open issues about
> libnotify? I guess that you should address the issues mentioned when
> this was rejected for 2.20, though they seem rather vague to me:
> http://mail.gnome.org/archives/devel-announce-list/2007-August/msg00004.html
>
> By the way, I am disappointed at the lack of API documentation,
> describing the "classes" and functions: I'm looking at this, for
> instance:
> http://www.galago-project.org/docs/api/libnotify/struct__NotifyNotification.html
>
> --
> murrayc murrayc com
> www.murrayc.com
> www.openismus.com
>
> _______________________________________________
> desktop-devel-list mailing list
> desktop-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/desktop-devel-list
>

-- 
Christian Hammond - chipx86 chipx86 com
VMware, Inc.