unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: guile-user <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: GNU G-Golf 0.8.0-rc-3 available for testing
Date: Wed, 17 Apr 2024 02:56:15 -0300	[thread overview]
Message-ID: <20240417025615.0b6c50f5@tintin> (raw)

[-- Attachment #1: Type: text/plain, Size: 3823 bytes --]

Hello Guilers,

The third release candidate 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-rc-3.tar.gz
	http://ftp.gnu.org/gnu/g-golf/g-golf-0.8.0-rc-3.tar.gz.sig

* Install

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

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

* Noteworthy changes in 0.8.0-rc-3

Here is a summary of the noteworthy changes in this release, also
available in NEWS file and on the G-Golf website.

** Dependencies

*** Adwaita examples

  Adw-1  >=  1.5.0

The adw1-demo has been updated, following upstream changes, so that most
of its demo pages now inherit and/or use the AdwDialog class, which is
available in Adwaita since 1.5.

** Examples

*** Adwaita Demo

The 'Navigation View' and 'Style Classes' pages have been updated to
inherit and/or use the AdwDialog Class.

The 'Dialogs' page has been updated to use the AdwAlertDialog class. It
also has been enhanced to properly support the async-api model, and,
while running the alert dialog callback, to dismiss any previsouly added
'Toast' if any.

** Bug fixing

*** Autotool chain

Changes has been made to support parallel installation as well as
cross-compilation.

*** Callback closure marshal(er)

The callback closure marshal(er) has been fixed to support callback with
'inout and 'out argument(s).

*** scm->gi-argument

Fixed to allow all GDestroyNotify callback functions to be nullable by
default.

* You can help

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

Consider joining us on irc [3], where you may ask for help or report a
problem [4].

However, if you prefer:

	G-Golf uses the guile-user@gnu.org mailing list
	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-rc-3.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!).

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2024-04-17  5:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240417025615.0b6c50f5@tintin \
    --to=david@altosw.be \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).