Jose Gabriel J Marcelino wrote:
>
> Hi,
>
> We're developing an application where we generate GladeXML interfaces
> in real-time from Perl using HTML::Mason.
> It's working fine, but we need to remove the embeded Perl code from the
> XML files before editing with the Glade builder and then put it back
> afterwards.
>
> This is a complicated step and solving it externally (using diff/patch, etc)
> is hard. A better solution would be for Glade to support XML comments, where
> we would put the code, like this:
>
> <widget>
> <class>GtkWindow</class>
> <name><!-- <& $win_name &> --></name>
> <title>window1</title>
> <type>GTK_WINDOW_TOPLEVEL</type>
> <position>GTK_WIN_POS_NONE</position>
> <modal>False</modal>
> <allow_shrink>False</allow_shrink>
> <allow_grow>True</allow_grow>
> <auto_shrink>False</auto_shrink>
> </widget>
> <!--
> % $m->comp("/comp/cust_widget.m">
> -->
>
> It's this type of support planned? Should I just try to patch
> the Glade code? Can someone just point me to the correct way
> of doing this within the Glade structure?
I can see that it would be useful to be able to bundle together the
interface
description and the code into one file for scripted languages like
Perl/Python.
Though I think that is already possible by using the libglade bindings
to create
the interface dynamically from an XML string, and then connecting the
signals.
Can't you do it that way instead? i.e. you generate the XML interface
description
as well as the Perl/Python script to load it using the libglade
bindings, and the
code for the signal handlers.
Damon
_______________________________________________
Glade-devel maillist - [EMAIL PROTECTED]
http://lists.helixcode.com/mailman/listinfo/glade-devel
