Re: G-Golf using GtkBuilder or not

David Pirotte <[email protected]> Thu, 29 May 2025 18:26:02 -0300
Newsgroups gmane.lisp.guile.user
Message-ID <20250529182602.3c449312@tintin>
Hi Zelphir,

> ...

You are misinterpreting what I wrote, and we miscommunicate.

GtkBuilder reads XML descriptions of a user interface and instantiates
the described objects. Those XML descriptions are largely identical
when defining a composite widget using a template, with some slight
differences, to quote the upstream doc:

	The interface description semantics expected in composite
	template descriptions is slightly different from regular
	GtkBuilder XML gtk_widget.

Templates do use gtk builders, as a matter of fact, Internally - just
so that you know, g-golf takes care of all this for its users -
gtk_widget_init_template() calls gtk_builder_set_current_object().

You could define your menu in a separate file, but that's not what the
(upstream) adwaita-1-demo does, and they really know what they are
doing ... however, if you persist, you'll find an example in the
gtk4-demo, Application Class.

For your app though, I strongly recommend that you template(s), in a
way that you should learn and 'copy' from the adwaita-1-demo g-golf
port.

This is my last msg wrt this subject.

David
signature.asc (application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEhCJlRZtBM3furJHe83T9k6MFetcFAmg40OoACgkQ83T9k6MF
eteZ5ggAy2RIWj1FCFdaK38LbfEgbNgoCyCKHDGnORaTKbfH5al7/++MSQEMWAE7
GCUtOAVrid1P5qBz15BLdDnJm1q3z58pSHVu/vKpBLQtTUYP5AL11K1OhYqxRW0h
jAPg+FpfeljhlXGFRHxrWVNyrb6OS95qw5s3cdJJNBQc7Cw18siij3BfxFFulRKH
g/U8HnsGzc6fQ3Hr4y8uiwpWS1UZiJgF48u/wtom/Hc754zSoQX13X46MPbVGNTa
rXbqkinv931VVOF0FfSnrF2jzvbbNgWncR19mP50peJ6sTokGVnT9FnHgOABQ+y0
8TabUhrAaDsastyNuxwOOSqAT4oPIA==
=1Oni
-----END PGP SIGNATURE-----