I was trying to work out what to do about the gnome extensions in
libglade. I think it would be best if there is only one libglade module
(so that we don't run into problems with binary packages).
What I was thinking of doing was creating a simple _libgladegnome module
as part of gnome-python which only contains the call to initialise the
gnome part of libglade. Then when libglade.py is loading, it checks for
this module, and if it exists initialises libglade-gnome. Alternatively,
you may want to have to explicitely initialise the gnome portion.
What do people think?
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On Tue, 21 Sep 1999, Paul Clifford wrote:
> Rick Ree wrote:
>
> [ ... ]
> > and a scrolled window with canvas. When I load the .glade file in
> > gnome-python a bunch of 'uknown widget class' warnings appear, in
> > particular for GtkPixmapMenuItem and GnomeCanvas.
>
> The Python glade bindings don't include support for GNOME widgets, which
> would explain the GnomeCanvas problem and possibly the GtkPixmapMenuItem
> message too (not sure if that's a GNOME widget or not). You could try
> changing the glade_init call in libglademodule.c to glade_gnome_init and
> see if that helps, although you'd then have difficulty distributing your
> program to others with "normal" gnome-python installations.
> To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
>
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
