Re: New modules in 2.14

["Gustavo J. A. M. Carneiro" <gjc inescporto pt>]

On Wed, 2006-01-18 at 09:48 +0800, Davyd Madeley wrote:
> On Tue, 2006-01-17 at 22:56 +0000, Gustavo J. A. M. Carneiro wrote:
> 
> > > So, I'm going a bit off-topic here, but I'm curious: what are these
> > > metacity python bindings for?
> > 
> >   They wrap libmetacity-private.  I think Johan wants to draw windows
> > inside a scrolled window in Gazpacho GUI builder, and that library
> > supposedly allows one to use metacity's rendering engine to immitate
> > metacity frames.  But I gues you already know this better than me :)
> > That's all I know about the bindings and the library, I'm afraid.
> > 
> >   I hope this is not a problem?..  libmetacity-private is a library
> > installed by a desktop module, hence it belongs in gnome-python-desktop,
> > I think.  These bindings were added before API/feature freeze.  And I do
> > expect to keep full control in the future of which bindings are added to
> > gnome-python-desktop as long as they wrap libraries of desktop modules.
> 
> Given the name "libmetacity-private", I don't think it's a good idea to
> be shipping public bindings to it. I don't think you could rely on this
> library to remain API stable. Of course, Elijah would have a better idea
> of this. Perhaps the solution is to create a libmetacity that use
> functions people may need to use, and a libmetacity-private to do
> whatever it is doing now.

  Sure it's not API stable, but neither is libwnck, yet many programs
use it with -DWNCK_I_KNOW_THIS_IS_UNSTABLE, or something like that.

  Would it help to rename the python module to metacity.private?

> 
> --d
> 
-- 
Gustavo J. A. M. Carneiro
<gjc inescporto pt> <gustavo users sourceforge net>
The universe is always one step beyond logic