|
A collection of modules that will read a <GTK-Interface>
XML file produced by the Gtk+/Gnome UI builder
Glade (versions <= 0.6.4),
construct and optionally show the UI using the Gtk-Perl bindings.
It is possible, using
Glade, for you to
specify a language of 'Perl' and generate source code from Glade's
'Build' button.
Glade-Perl can write the perl modules to construct/run the UI together with a skeleton "App" and a working subclass for you to edit. The modules generated are pretty much OO code and can be combined and split in any way that you wish. Glade-Perl will generate code to construct all the widgets that Glade knows about apart from the GnomeDb ones. However, the gnome-libs are not necessary and you can work quite happily without them - but of course you cannot then use the Gnome widgets in your UI. You can read the online documentation or download Glade-Perl and find software that we depend on. Glade-Perl is still beta software so please don't use it to generate code to control heart-lung machines or manned space missions. |
|
A collection of modules that will read a <glade-interface>
XML file produced by the Gtk+/Gnome UI builder
Glade-2 (versions >= 1.1.0),
construct and optionally show the UI using the Gtk-Perl bindings.
It should be possible, using
Glade-2 from version 1.1.4, for you to
specify a language of 'Perl' and generate source code from Glade's
'Build' button.
Glade-Perl-Two can write the perl modules to construct/run the UI together with a skeleton "App" and a working subclass for you to edit. The modules generated are pretty much OO code and can be combined and split in any way that you wish. Glade-Perl-Two will generate code to construct all the widgets that Glade-2 knows about apart from the Gnome and GnomeDb ones. You can read the online documentation or download Glade-Perl-Two and find software that we depend on. Glade-Perl is still beta software so please don't use it to generate code to control heart-lung machines or manned space missions. |
I apologise to XML gurus - I know that this is the 'wrong way round' to build a DTD and the script probably doesn't even generate correct code. It will probably generate wierdness from non-ascii (eg Latin1) XML and it ignores any existing DTD subsets that are specified (internal or external).
The script uses perl modules XML::Parser and XML::Grove (available from CPAN).
It is not a very good script, please send me fixes if you think that it is worth fixing. Download file XML-DTD (4kb)