Shilad Sen wrote:
>
> Hello,
>
> I am thinking about using glade for a large scale application in
> which we would have to add a couple new widgets.
>
> I know there is support through the "Custom Widget", but I don't think
> this is what we are looking for. We would actually like to be able to
> see the new widgets that we are adding in the way they look.
>
> Is the easiest way to do this to recompile glade, adding new widgets
> (and possibly a new palette) for the widgets that we need?
>
> I notice there appeared to be an attempted at plugin support for
> additional widgets through glade_plugin_load_plugins. It doesn't
> seem that this has been worked on for a while. 0.5.11 has this
> code commented out. Does anybody know if there is a reason? Does
> this code not work?
>
> Any help would be much appreciated.
>
This is an answer from a non-Glade developer :)
I use glade for the Smurf Sound Font Editor
(http://smurf.sourceforge.net) and have a number of custom widgets.
Unfortunately glade doesn't seem to currently have a nice way to add
these to an interface. The "Custom Widget" option is a neat idea but
requires the creation function to have a fixed # and type of parameters
which is a bit dirty for my programming taste. It would be nice if this
Glade function allowed you to just specify the # of parameters it had
and then just gave you that many text fields to fill, and insert the
text exactly as it is in the function call, type checking would then be
done by the compiler. In fact I rarely have any parameters to my custom
widget creation functions, so I don't like the idea of having to make a
wrapper for them. Even after getting past this though, you still can't
see the widget in the builder of course. So I just opted to code it the
old fashion way.
I think another nice addition to the custom widget idea (somewhat
related) would be to allow building of "non-dialog" based interface
elements. Currently creating interfaces requires that they be within a
dialog. Seems like there could be many uses for using glade to build
elements that are in a box or whatever. I have seen this discussed on
this list before.
The other nit pick I have with using Glade is the inability to turn off
the auto insertion of callback declarations. While I can see the use of
this for smaller applications that have all glade callback routines in
one file, its a little bit of a pain when callbacks are spread out
between multiple files (the case with Smurf). It just means that every
time I connect to a signal I have to open up two files
(glade_callbacks.c and .h) and erase the declarations Glade put in them.
Actually that one has been bothering me for some time. I should probably
just get the latest Glade and code an option for disabling this function
:)
I like glade a lot though. It has saved me lots of time in building UI
stuff. I especially like the ability to easily change interface elements
without having to re-work tons of GTK code. Lates..
Josh Green
_______________________________________________
Glade-devel maillist - [EMAIL PROTECTED]
http://lists.helixcode.com/mailman/listinfo/glade-devel
