RE: GAL, glade and libglade

[Franck Martin <Franck sopac org>]

I would suggest a small piece of software that walk in the developper inside
its own widget.  Given a path, the software would read all the libraries and
find out if they are gtk or gnome libs, then extract all the widgets from
there, and extract all the parameters from gtkArgs.

I have been complaining in the past about certain widget (CTREE, OPTION) not
exposing through function certain internal status, which have to be
extracted by knowing the internal C structures. With the above tool, it
would be easy for the developer to know the widget capabilities it offers,
and also help him design its own widgets and see what functions are exposed
to other users/developers... Simple developer Manuals could then be produced
out of all that.

Cheers.

Franck Martin
Network and Database Development Officer
SOPAC South Pacific Applied Geoscience Commission
Fiji
E-mail: franck sopac org <mailto:franck sopac org> 
Web site: http://www.sopac.org/
<http://www.sopac.org/> Support FMaps: http://fmaps.sourceforge.net/
<http://fmaps.sourceforge.net/> 

This e-mail is intended for its addresses only. Do not forward this e-mail
without approval. The views expressed in this e-mail may not be necessarily
the views of SOPAC.



-----Original Message-----
From: James Henstridge [mailto:james daa com au]
Sent: Monday, 12 February 2001 1:54 
To: Miguel de Icaza
Cc: Lee Mallabone; gnome-devel-list gnome org; damon ximian com
Subject: Re: GAL, glade and libglade



On 11 Feb 2001, Miguel de Icaza wrote:

> 
> 
> > Is removing the (seemingly small) libglade dependency in GAL something
> > that Miguel will consider a patch for? (or whichever maintainer is most
> > appropriate) 
> 
> Not really, because if anything we are starting to use more Glade in
> Gal than in the past.  Now the dependency in Gal is for libglade.
> 
> There are a few alternatives for the problem you have:
> 
> 	* Use Bonobo-based widgets (lots of work to do, but pretty
>           straight forward).
> 
> 	* Design a widget registration mechanism for libglade.  Needs
>           some design consideration, and would not require a lot of
>           work, but a lot of re-released packages.

It has been possible to register new widget types with libglade since the
first release I made.  You just need a bit of glue code to apply the
widget properties in the glade file to the new widget.

If all widgets were fully customisable from the GtkArg interfaces, then
this glue code could probably go as well.  I guess this is something to
aim at for gtk 2.0/gnome 2.0

James.

-- 
Email: james daa com au
WWW:   http://www.daa.com.au/~james/



_______________________________________________
gnome-devel-list mailing list
gnome-devel-list gnome org
http://mail.gnome.org/mailman/listinfo/gnome-devel-list