Re: Slab's CC
- From: Rodrigo Moya <rodrigo novell com>
- To: Denis Washington <dwashington gmx net>
- Cc: gnomecc-list gnome org
- Subject: Re: Slab's CC
- Date: Wed, 11 Oct 2006 21:49:34 +0200
On Wed, 2006-10-11 at 18:04 +0200, Denis Washington wrote:
> Rodrigo Moya wrote:
> > On Wed, 2006-10-11 at 17:41 +0200, Denis Washington wrote:
> >
> >> Rodrigo Moya wrote:
> >>
> >>> CCing desktop-devel-list for any comment:
> >>>
> >>> On Tue, 2006-10-10 at 18:08 +0200, Rodrigo Moya wrote:
> >>>
> >>>
> >>>> On Tue, 2006-10-10 at 11:58 +0200, Rodrigo Moya wrote:
> >>>>
> >>>>
> >>>>> Hi
> >>>>>
> >>>>> I'm starting to move code from the CVS module slab to our
> >>>>> control-center. So, this means just moving the slab/control-center code
> >>>>> to our module, which is easy. The problem is with libslab/libtile and
> >>>>> the util/ dir. The idea so far has been to leave them in slab and set
> >>>>> them up as virtual modules for control-center and later, if accepted,
> >>>>> into the panel (for the slab's menu applet).
> >>>>>
> >>>>> But I just started thinking about having all this code into a
> >>>>> libgnomecontrolcenter that, later, if accepted, the panel could use.
> >>>>> What do you think?
> >>>>>
> >>>>>
> >>>> Following on this, I'm looking (and almost starting) to merge all the
> >>>> libs we have in c-c into a single libgnomecontrolcenter library. That
> >>>> means putting libbackground and libwindow-settings, and, if we all
> >>>> agree, libslab and libtile (while we look for a better place).
> >>>>
> >>>> Anyone has anything against this? I guess we don't have ABI/API
> >>>> problems, since they're not platform libraries, right?
> >>>>
> >>>>
> >> Personally, I think moving slab into a libgnomecontrolcenter would be a
> >> bit inconvenient if it might also be used in the panel. I mean, why
> >> should gnome-panel depend on a gnomecc library?
> >>
> >>
> > let me answer you with a question :) why should the panel, and the c-c,
> > depend on 2 more libraries (libslab and libtile), not in the platform?
> >
> > Of course, we could solve it by adding both libs to both modules as
> > virtual CVS dirs, but that means having 2 copies of the same library in
> > 2 apps that are running always in all gnome desktops. Of course, not a
> > huge problem, but why should we prefer that over a clean and, hopefully
> > in the future, in the platform, libgnomecontrolcenter?
> >
>
> Well, OK, you're right in this respect :). My actual concern is the
> naming "libgnomecontrolcenter" for a library that is both used by
> gnome-cc and the panel. But to be honest I don't know a better name ;),
> so I don't really mind if we just stick with libgnomecontrolcenter.
>
good point, and in fact having that libgnomecontrolcenter is a first
step towards the wider libgnomeextensions that has been mentioned in the
'GNOME desktop integration lib' thread on d-d-l. So yeah, I guess we
want to start having it in control-center, and as we clean it up and
make it better, put it in a common place for all GNOME apps to use it.
Also, having the panel depend on the c-c shouldn't be that hard if we,
as I've been thinking, splitted the capplet from it. The c-c would just
then be the lib and the settings daemon.
--
Rodrigo Moya <rodrigo novell com>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]