From: MSavoritias <email@msavoritias.me>
To: Greg Troxel <gdt@lexort.com>, guile-user@gnu.org
Subject: Re: status of guile-gnome and replacements?
Date: Tue, 7 Nov 2023 16:47:53 +0200 [thread overview]
Message-ID: <1989a0ad-9d6a-110f-ddab-0c15d2e6a875@fannys.me> (raw)
In-Reply-To: <rmipm0liq7s.fsf@s1.lexort.com>
On 11/7/23 16:37, Greg Troxel wrote:
> In pkgsrc we are pruning gnome2 (but have mate). That's not about
> guile, but it is causing a hard look at things that depend on gnome2.
>
> We have guile-gnome 2.16.5, the most recent release, released in June of
> 2017. I remember using something in 2004ish, but more for gtk than
> gnome.
>
> Our package depends on guile 2.0. I just tried to run calc.scm which I
> remember from the old days, but it failed, perhaps due to how we
> namespace multiple guile versions.
>
> I tried to find what guile-gnome has been replaced by, and remembered
> g-wrap, but last release was 2015 and it's a FFI.
>
> I then found guile-gtk, from 2007 which says to use guile-gnome.
>
> I found guile-cairo, from 2020 which counts as recent, but "Guile-Cairo
> is complete, wrapping almost all of the Cairo API." which does not seem
> to be "you can use this to do random gtk3 things".
>
> So: what is the current best way to do gtk3 (4?) from guile?
>
> At this point I have no need, but I like to see guile things live on,
> when it makes sense. But it is seeming like tilting at windmills to
> keep guile-gnome going.
>
> What do other packaging systems do? Debian 12 doesn't have guile-gnome
> but it does have guile-cairo.
>
> Greg
>
As far as i know the most maintained and best way to use gtk/gnome
things from guile is guile-gi https://github.com/spk121/guile-gi
Regards,
MSavoritias
next prev parent reply other threads:[~2023-11-07 14:47 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 [this message]
2023-11-07 16:22 ` Mike Gran
2023-11-08 3:19 ` David Pirotte
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=1989a0ad-9d6a-110f-ddab-0c15d2e6a875@fannys.me \
--to=email@msavoritias.me \
--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).