Cleaning up libxfcegui4...

Benedikt Meurer benedikt.meurer at
Wed May 3 19:11:45 CEST 2006

Erik Harrison wrote:
>>libxfcegui4 was extended with more and more stuff since the pre-4.0
>>days, and now contains probably more deprecated functionality than
>>useful functionality. Also, half of the library is not useful to many
>>applications (the netk stuff), while some applications like xfwm4 need
>>only the netk stuff and not the rest (well, the event filter stuff, but
>>that in turn is only used by xfwm4 so it should be moved to xfwm4).
>>I'd like to cleanup libxfcegui4 this way:
>>a) Put all netk stuff into libnetk, and
>>b) Start with a fresh and clean libxfce4ui (or another name, tho
>>libxfce4ui would be finally consistent with libxfce4util/libxfce4mcs),
>>containing only the dialog widget with the header mentioned in the
>>previous mail, and
>>c) let libxfcegui4 depend on libnetk and libxfce4ui.
> How long do you propose this version of libxfcegui4 hanging around.
> Especially in the case of netk, lots of panel plugins, which are
> poorly maintained anyway, depend on that library. If we toss
> libxfcegui4 for, say 4.8, that's fine, but if it goes in 4.6 then the
> interface for panel plugin writers just changes too often to expect
> plugin writers to keep up.

We can keep libxfcegui4 around for some time, as simple wrapper to
libxfce4ui and libnetk, with the otherwise deprecated widgets. But I
think one year for 4.6 should be enough to drop libxfcegui4 completely.
Panel plugins that haven't been updated within this time may not work
with xfce4-panel then anyway.


More information about the Xfce4-dev mailing list