From: David Pirotte <david@altosw.be>
To: Greg Troxel <gdt@lexort.com>
Cc: guile-user@gnu.org
Subject: Re: status of guile-gnome and replacements?
Date: Wed, 8 Nov 2023 00:19:25 -0300 [thread overview]
Message-ID: <20231108001904.7eef1384@tintin> (raw)
In-Reply-To: <rmipm0liq7s.fsf@s1.lexort.com>
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
> ...
> So: what is the current best way to do gtk3 (4?) from guile?
You should (highly) consider using Adwaita instead (libadwaita),
and gtk-4 for what ever isn't customized (yet) in libadwaita.
But to address your question (disclaimer, I am its maintainer), as Mike
already did suggest, you should use g-golf [1].
Regards,
David
[1] which by the way comes with gtk-4 examples as well as a port
(wip) of the upstream adwaita-1-demo. Images (screenshots) of those
examples here: https://www.gnu.org/software/g-golf/learn.html
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-11-08 3:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 14:37 status of guile-gnome and replacements? Greg Troxel
2023-11-07 14:47 ` MSavoritias
2023-11-07 16:22 ` Mike Gran
2023-11-08 3:19 ` David Pirotte [this message]
2023-11-10 14:15 ` Greg Troxel
2023-11-08 3:27 ` David Pirotte
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=20231108001904.7eef1384@tintin \
--to=david@altosw.be \
--cc=gdt@lexort.com \
--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).