Hello Guilers,

The sixth alpha release of the upcoming GNU G-Golf 0.8.0 release is
now available for testing:

-]	Tarball and a GPG detached signature [*]:

		http://ftp.gnu.org/gnu/g-golf/g-golf-0.8.0-alpha-6.tar.gz
		http://ftp.gnu.org/gnu/g-golf/g-golf-0.8.0-alpha-6.tar.gz.sig

-]	Dependencies and complete installation instructions are given
	in the distributed INSTALL file, or here:

		https://www.gnu.org/software/g-golf/install.html

-]	Here is a summary of the noteworthy changes in this release,
	also available in NEWS file and on G-Golf's site

* Dependencies

- Core dependencies

The guile-lib dependency has been removed from the core dependencies, as
it effectively is only required to run the test-suite.

- Test suite

The test-suite requires guile-lib >= 0.2.5
The test-suite no longer requires Clutter.

- Adwaita examples

  Adw-1  >=  1.4.0

The adw1-demo - which currently implements the main window, primary menu
and first two pages (wip) - has been updated to correspond to the latest
upstream version, which no longer uses the deprecated AdwLeaflet*
classes. Instead, it uses the AdwNavigationSplitView, AdwNavigationView
and AdwNavigationPage classes, available since 1.4.0.

* New features

Derived class
GObject properties

  Derived classes slot exposed as a gobject property now also support
  the object type - Wip (supported type are now int, enum and object).

disconnect

New method, which calls the newly added g-signal-handler-disconnect
binding.

* Examples

Adwaita Demo

The adw1-demo - which currently implements the main window, primary menu
and first two pages (wip) - has been updated to correspond to the latest
upstream version, which no longer uses the deprecated AdwLeaflet*
classes. Instead, it uses the AdwNavigationSplitView, AdwNavigationView
and AdwNavigationPage classes, available since 1.4.0.

* Bug fixing

g-value-set-boxed

Was silently setting the g-value to #f for opaque boxed type, fixed.

connect
signal-connect

Now return the handler-id, needed to call disconnect.

-]	You can help by:

  1. Testing by installing from the tarball, or from the source if you
  prefer, on the distro of your choice.

  2. By running the distributed examples.

Ultimately, one of the best way to test, and participate, is to select
G-Golf to develop the next application of your dream! Here is an
overview of the GNOME platform libraries [1], accessible using G-Golf.
In particular, libadwaita [2] provides a number of widgets that change
their layout based on the available space. This can be used to make
applications adapt their UI between desktop and mobile devices (as
shown in the G-Golf port of the "Adwaita demo").

-]	Contact [3]

Before you email, or send a bug report, you could join us on irc, and
ping me there, my preferred way to quickly interact and fix potential
G-Golf problem(s) [4].

However, if you prefer:

	G-Golf uses Guile's mailing lists
	Report bugs to bug-g-golf@gnu.org


Thanks!
David


[*] Use a .sig file to verify that the corresponding file (without the
    .sig suffix) is intact.  First, be sure to download both the .sig
    file and the corresponding tarball.  Then, run a command like this:

	gpg --verify g-golf-0.8.0-alpha-6.tar.gz

    If that command fails because you don't have the required public
    key, then run this command to import it:

	gpg --keyserver keys.gnupg.net --recv-keys A3057AD7

    and rerun the 'gpg --verify' command


[1] https://developer.gnome.org/documentation/introduction/overview/libraries.html
[2] https://gnome.pages.gitlab.gnome.org/libadwaita/doc/main/
[3] https://www.gnu.org/software/g-golf/contact.html

[4] When reporting a problem, or if you think you found a bug, it is
very important that you prepare a minimal reproducible example (MRE),
sometimes also referred to as a short self-contained correct example
(SSCCE)

	http://www.sscce.org/
	https://en.wikipedia.org/wiki/Minimal_reproducible_example

Also, on irc, we chat :), so please do not write code snipsets directly
in the channel, unless 2 or 3 lines of code, nor error messages of
course - for more then 2 or 3 lines of code, or error messages, always
use a tor-friendly paste service (avoid those that track its visitors
and require javascript, thanks!).