Cleaning up libxfcegui4...

Benedikt Meurer benedikt.meurer at
Wed May 3 00:26:18 CEST 2006

Stephan Arts wrote:
>>>Another option would be to move the useful stuff from libxfcegui4 to
>>>libexo (and the netk stuff to libnetk) and let applications use libexo
>>>instead of libxfcegui4 (over time). This would require moving the
>>>"Preferred Applications" MCS plugin to xfce4-mcs-plugins, tho, to
>>>resolve the cyclic redundancy.
>>Err, redundancy = dependency. ;-)
>>And while thinking about this again, depending on how Xfce should look
>>and work in the future, this may be the best option.
> I agree.
> I am interested in your ideas about this regarding the other two libraries?
> libxfce4utils and libxfce4mcs? Or am i going off-topic here?

I cleaned up libxfce4util recently. It doesn't contain any deprecated
stuff, except xfce_strip_context(). We need to keep libxfce4mcs around
until we have a replacement for MCS, which is not going to happen for
Xfce 4.4. We'll see to this later.

Also, libxfce4util and libxfce4mcs do not really present a problem here.
For example compare the sizes of the various libraries (stripped):


   text    data     bss     dec     hex filename
 226560    3488     304  230352   383d0
 266132   10440     544  277116   43a7c
  49754     952    1184   51890    cab2
  13948     804      52   14804    39d4
  20175     908      52   21135    528f
 173496    4908     484  178888   2bac8
  31191    1184     112   32487    7ee7

libxfce4util's bss size is kinda confusing, I guess part of the problem
are the various static locks, but that's still a lot. But as you can
see, libxfcegui4 is the biggest player in town, even tho only a few bits
of the library are still in wide use today.


More information about the Xfce4-dev mailing list