Comments on: libsexy is not libegg

By: Tristan

Tristan — Sat, 03 Mar 2007 03:51:14 +0000

Consider writing a plugin to glade

If a glade/libglade plugin exists and is installed, then
the libsexy widgets will show up in glade… I’m sure this
would help encourage people to use libsexy as a widget kit
proper instead of just a heap of code

By: Jon

Jon — Fri, 02 Mar 2007 09:51:42 +0000

Debian Etch and Ubuntu Edgy ship libsexy. It also seems to be a dependency of the gnome-core, rhythmbox and xchat packages (but not gedit).

(gah three tries on the evil captcha to write this)

By: ChipX86

ChipX86 — Fri, 02 Mar 2007 08:45:15 +0000

Jon, James: Oh, I wasn’t aware of this. This makes a lot of sense. My understanding was that most distros now ship libsexy, though I guess FC7 doesn’t. Huh. Given how popular Rhythmbox is, I bet the distros will bundle it if it’s a dependency. Still, using the system’s libsexy takes care of my concerns. Thanks for clearing that up

By: James "Doc" Livingstom

James "Doc" Livingstom — Fri, 02 Mar 2007 06:19:04 +0000

Rhythmbox uses the shared library if it’s present when RB is compiled, and only uses the internal copy as a fallback. The reason we have it as a fallback was that at the time, virtually none on the released distros had libsexy, only the in-development versions – so if we wanted to use it, it was basically a choice between having a fallback copy, or falling back to the standard GTK widgets.

If most distros now ship it, we could probably remove the fallback.

By: random dude

random dude — Fri, 02 Mar 2007 05:57:57 +0000

> then discuss ways of fixing up GTK for GTK+ 3.0

I think the time to start discussing this is now. You should file everything libsexy provides as feature requests against gtk+.

By: Jon

Jon — Fri, 02 Mar 2007 05:34:04 +0000

Rhythmbox will use the system’s version of libsexy if it is available. However, there are enough systems that don’t have libsexy available by default that it is necessary to use a private copy… or not use it at all.

By: Andrew

Andrew — Fri, 02 Mar 2007 01:29:08 +0000

Fedora doesn’t ship libsexy, and at least as far as Rawhide (F7 test) they still are shipping a patch that strips libsexy out of the notification-daemon.
Maybe they’ll rethink that when Extras is merged in F7.

By: ChipX86

ChipX86 — Fri, 02 Mar 2007 00:56:39 +0000

anonim: I answered that.

By: anonim

anonim — Thu, 01 Mar 2007 23:31:58 +0000

yes, why don’t integrate entire libsexy into gtk?

By: ChipX86

ChipX86 — Thu, 01 Mar 2007 23:31:52 +0000

I’m very much in favor of moving the libsexy components to GTK+. However, a lot of what libsexy does could be considered “hacks” as they extend existing widgets in ways that they really weren’t meant to be extended. The proper path is to fix up the widgets, but that’s potentially dangerous for backwards-compatibility. I’m thinking that the best course of action is to have people use libsexy for now and then discuss ways of fixing up GTK for GTK+ 3.0.

Michael: I don’t think this has been pointed out to me (or I’ve missed it). I’d be glad to get this fixed up.