This is now available on macOS via Guile Homebrew: brew install g-golf
On Wed, Nov 1, 2023 at 8:51 PM David Pirotte <da...@altosw.be> wrote: > Hello Guilers, > > The second 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-2.tar.gz > http://ftp.gnu.org/gnu/g-golf/g-golf-0.8.0-rc-2.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-2 > > Here is a summary of the noteworthy changes in this release, also > available in NEWS file and on the G-Golf website. > > ** Examples > > Adwaita Demo > > The 'Dialogs' page has been added to the demo. > > ** Bug fixing > > emit > signal-emit > > Fixed to properly handle 'object extra arg(s) type. Prior to this fix, a > call such (emit window 'add-toast toast), with window and toast being > goops proxy instances, would raise an exception, as the extra args > handler missed a proper dispatch clause and treatment for the 'object > arg type, > > * 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-u...@gnu.org mailing list > Report bugs to bug-g-g...@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-2.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!). >
