Re: Layout Composite Widget Components Using Glade-3? / Pluggable widgets replacement for Glade custom widget?

[Daniel Yek <dyek real com>]

Tristan Van Berkom wrote:
> On Thu, Oct 16, 2008 at 10:01 PM, Daniel Yek <dyek real com> wrote:
>   
> > ...create a (custom) composite widget to contain several standard GTK+ widgets...(It is nicer if all widgets 
> > appear in the same design view.)
> >
> > ...Is pluggable widget the replacement mechanism for custom widget?
> >
> > I read a little about pluggable widgets, but I'm not familiar with creating
> > pluggable widgets and I am likely not able to spend time on that. How much
> > additional time is needed to turn a custom widget into a pluggable widget?
> >     

> > Is there a generic mechanism that automatically turn a custom widget into a
> > pluggable widget where it might be possible? :-)
> >     
> Well, in trunk you are allowed non GtkWindow toplevel objects, and you are
> allowed to use a more lax naming scheme - so it can be as easy as defining some
> widget layouts in glade... and then the art is how you parse it with gtkbuilder.
>
> you should be able to use builder first to build your main window, and then
> go back in the file and build your other "composed" widgets seperately,
> and just add them to your interface with gtk_container_add() yourself.
>   

Interesting! Thanks for the information.

> Glade can also integrate your own real custom GtkWidget derived object
> into the runtime, thats why we deprecated the old custom widget hook.
>   

This is done by installing custom widgets catalog into catalog 
directory, installing custom plugin libraries, loading optional/custom 
plugin libraries, installing and loading glade-3 custom widget icons, right?

If so, is this not the pluggable widget that I referred to earlier?

Thank you.

--
Daniel Yek.

> Cheers,
>                     -Tristan
>