Re: libnotify, notification-daemon and gnome desktop modules



On Tue, Feb 07, 2006 at 09:38:24AM +0100, Vincent Untz wrote:
> Hey,
> 
> Le lundi 30 janvier 2006 ?? 17:44 -0700, Elijah Newren a ??crit :
> > On 1/30/06, Christian Hammond <chipx86 chipx86 com> wrote:
> > <snip>
> > > It's being used by more and more programs. xchat-gnome is a good
> > > example. It should be okay as a dependency (though I'm biased ;).
> > 
> > Okay, let's bring it up on d-d-l suggesting that and see if there are
> > any objections, brutally beating down any opposition where necessary. 
> > Oh, um, except maybe for that last part.  I don't really expect people
> > to be opposed though.  Anyway, John, do you want to handle bringing it
> > up there?
> 
> Well... To be honest, I don't really like the idea of bringing yet
> another library in the desktop: we're trying to consolidate our
> libraries with Ridley and adding another library is just another way to
> defeat this goal.
> 
> If the widgets in libsexy are useful, then they should really be
> proposed for inclusion in GTK+.

This is a lot of work and while I would like some of these widgets to
go into GTK at some point, I don't expect they would as-is. Getting
these into GTK would involve "doing it right," and libsexy makes use
of GTK in ways that almost nothing else does. The "right way" would be
to extend GTK further, but this is a longer project.

notification-daemon *requires* libsexy. It can't be made an optional
dependency, as SexyUrlLabel, part of libsexy, is the only way of
providing a block of text without decorations that can contain inline
hyperlinks.

More and more applications are starting to use libsexy, and nearly
every upcoming desktop distro is now shipping it. Is this really such
a problem? Isn't it better to get this in so more apps can take
advantage of it and push for getting it into GTK when it can be done
properly?

Christian
 
-- 
Christian Hammond         <>  The Galago Project
chipx86 chipx86 com       <>  http://www.galago-project.org
   The major difference between a thing that might go wrong and a thing that
   cannot possibly go wrong is that when a thing that cannot possibly go wrong
   goes wrong it usually turns out to be impossible to get at or repair.

Attachment: signature.asc
Description: Digital signature



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]