Help language development. Donate to The Perl Foundation
Due to the latest developments in Gnome::Gtk3, this package gets less interesting. The reason for it being the addition of a method .gtk_builder_connect_signals_full()
in module Gnome::Gtk3::Builder which does more or less the same as Gnome::Gtk3::Glade::Work and Gnome::Gtk3::Glade::Engine. The only thing interesting left here is the testing module which is still undocumented and unfinished and also planned to go into something like Gnome::T.
Here is an example taken from the Builder module;
my Str $ui = q:to/EOUI/; <?xml version="1.0" encoding="UTF-8"?> <interface> <requires lib="gtk+" version="3.20"/> <object class="GtkWindow" id="top"> <property name="title">top window</property> <signal name="destroy" handler="window-quit"/> <child> <object class="GtkButton" id="help"> <property name="label">Help</property> <signal name="clicked" handler="button-click"/> </object> </child> </object> </interface> EOUI # First handler class class X { method window-quit ( :$o1, :$o2 --> Int ) { # ... do something with options $o1 and $o2 ... Gnome::Gtk3::Main.new.gtk-main-quit; 1 } } # Second handler class class Y { method button-click ( :$o3, :$o4 --> Int ) { # ... do something with options $o3 and $o4 ... 1 } } # Load the user interface description my Gnome::Gtk3::Builder $builder .= new; my Gnome::Gtk3::Builder $builder .= new(:string($ui)); my Gnome::Gtk3::Window $w .= new(:build-id<top>); # It is possible to devide the works over more than one class my X $x .= new; my Y $y .= new; # Create the handlers table my Hash $handlers = %( :window-quit( $x, :o1<o1>, :o2<o2>), :button-click( $y, :o3<o3>, :o4<o4>) ); # Register all signals $builder.connect-signals-full($handlers);
With the modules from package Gnome::Gtk3
you can build a user interface and interact with it. This package however, is meant to load a user interface description saved by an external designer program. The program used is glade which saves an XML description of the made design.
The user must provide one or more classes containing methods to receive signals defined in the user interface design. Registration of signals will be done automatically.
Then only two lines of code (besides the loading of modules) is needed to let the user interface appear and enter the main loop.
The first thing to do is designing a ui and save it. A part of the saved result is shown below. It shows the part of an exit button. Assume that this file is saved in example.glade.
<?xml version="1.0" encoding="UTF-8"?> <!-- Generated with glade 3.20.0 --> <interface> <requires lib="gtk+" version="3.0"/> <object class="GtkWindow" id="window"> ... <object class="GtkButton" id="quit"> <property name="label">Quit</property> <property name="visible">True</property> <property name="can_focus">False</property> <property name="receives_default">False</property> <signal name="clicked" handler="quit-program"/> </object> ... </interface>
Then write code to handle all signals which are defined by the user interface. These modules are called engines. You do not have to write every handler at once. You will be notified about a missing handler as soon as an event is fired for it.
Only the method to handle a click event from the quit button is shown below in the example. This example file is saved in lib/MyEngine.pm6.
use v6; use Gnome::Gtk3::Glade; use Gnome::Gtk3::Glade::Engine; unit class MyEngine; also is Gnome::Gtk3::Glade::Engine; # $widget is the activated button after which this method is called. Methods # are from Gnome::Gtk3::Button. See documentation in the Gnome::Gtk3 project. method quit-program ( :$widget ) { note "Button label: ", $widget.get-label; note "Button name is by default button's class name: ", $widget.get-name; self.glade-main-quit(); } ...
The rest is a piece of cake.
use v6; use MyEngine; use Gnome::Gtk3::Glade; my Gnome::Gtk3::Glade $gui .= new; $gui.add-gui-file("example.glade"); $gui.add-engine(MyEngine.new); $gui.run;
zef install Gnome::Gtk3::Glade
Name: Marcel Timmerman Github account name: MARTIMM