Andrae Muys wrote:
> > Glade was one of the first GTK+/Gnome projects to use XML. I don't think
> > libxml was around then. I'd like to switch over to it now, though.
>
> So it is a historical reason, and the reason is no longer relevant. In
> that case would you accept a patch to support libxml? OTOH, I know that
> hp would like to see libglade made a part of Gtk+,
Really? I don't remember hp saying that.
I think if GTK+ includes a way to load XML interface definitions it should
use GParams, and so would use generic code to load all widgets.
I don't think they should include libglade for this.
(This is one of the reasons GParam support is important. It makes dynamic
loading of interface definitions trivial, and supports any widgets.)
> for this to happen we
> would need to use GMarkup instead. Now I have had a look at the Glade
> XML format, and I don't think we would have to change anything to
> support GMarkup instead of libxml. However GMarkup dosn't support
> attributes. I don't think Glade uses attributes anywhere, but if I've
> missed something that would require a format change. The advantage of
> using GMarkup over libxml is that GMarkup is a standard part of Glib2.0,
> while libxml will always remain a seperate library.
>
> Any thought's on this?
That may be a bit of a limitation.
I think for Glade we should use libxml, in case we do decide we need more
XML features like attributes.
> > > My specific question is this: Can I rely on _set_properties() being
> > > called once for each property, or do I have to always set ALL the
> > > properties of a widget EVERY time it's called?
> >
> > No. When loading all the properties are set in one go.
>
> Would you accept a patch to fix this? I am really uncomfortable with
> having two modules assuming a different contract with the same function.
Why is it causing a problem?
I wouldn't want to change it unless it was really needed.
> > > Also, regarding the properties sheet. I want to dynamically add/delete
> > > properties at run-time. Is there an easy way to do this? At the moment
> > > I'm planning on abandoning the properties sheet and just using an
> > > external dialog along the lines of gbmenubar.
> >
> > All the widget-specific properties are added at runtime already, in the
> > gb_*_create_properties() functions.
> >
> mmm that wasn't what I meant. I still consider this compile-time, as
> the properties concerned are still compiled into glade, even if they're
> in a different module. What I meant was the ability to add and
> specifically *delete* properties from the properties dialog in response
> to user actions.
What is this for exactly? What kinds of user actions?
Aren't the property_add_*() functions enough for adding properties?
There isn't a function to delete properties but you may be able to add it
by basically doing the opposite of property_add().
Are you trying to support external libraries containing all the GbWidget
functions, or with GtkArg/GParams?
Damon
_______________________________________________
Glade-devel maillist - [EMAIL PROTECTED]
http://lists.helixcode.com/mailman/listinfo/glade-devel
