Re: libwnck status & gnome-core

[Havoc Pennington <hp redhat com>]

Michael Meeks <michael ximian com> writes:
> 
> 	It concerns me greatly that we are installing this brand new, untried,
> and self-confessed "doesn't work yet" and needs a
> -DWNCK_I_KNOW_THIS_IS_UNSTABLE to work on compile.
> 

We can change it to
WNCK_I_KNOW_THIS_IS_PRIVATE_AND_HAS_NO_ABI_GUARANTEES which is what
UNSTABLE means here. It doesn't mean the code is buggy or
untested. The README is I suppose outdated since it has now been
tested in gnome-core and certainly works at least as well as
gnome-core itself. ;-)

> 	So - if no-one screams shortly, I'll do the CVS surgery to move this
> into gnome-core with a virtual CVSROOT whatnot, and a AC_CONFIG_SUBDIRS
> type thing.

No, don't do that. It's deliberately (on my part) an installed
library, because for GNOME 1 we had cut-and-pasted the equivalent
functionality all over creation, because procman wanted to use it, and
because I want to encourage some experimentation on the pager/tasklist
front (application-based instead of window-based tasklist/appmenu for
example would be neat).

The -D is simply to clarify its non-platform API-unfrozen status.  I
think all non-platform libs should consider such a -D to keep users
from accidentally hosing themselves.

Havoc