From: Luis Felipe <luis.felipe.la@protonmail.com>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: guile-user@gnu.org
Subject: Re: understanding guile-gi
Date: Sun, 16 Jan 2022 16:24:20 +0000 [thread overview]
Message-ID: <KyQcY4cBaWPTmOn1pDYy67i9ZHpPNE17aWJ8IosFE8UasgIXIS5IF8gepwjjlZXCUl5jp80IC6fPD7ouKmFk_JDy4NxEpzjh_olZqq6G9eM=@protonmail.com> (raw)
In-Reply-To: <f58b8502-d64d-d7e0-b9f3-0d3276bfae68@posteo.de>
[-- Attachment #1.1: Type: text/plain, Size: 787 bytes --]
Hi
On Sunday, January 16th, 2022 at 1:37 PM, Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> wrote:
> guile-gi – I think this stands for "Guile Gnome(?) Introspection"?
It's GObject Introspection: https://gi.readthedocs.io/en/latest/
Many libraries become available through GI, not only GTK.
> And finally: Is my expectation correct, that I will be able to make GTK applications using Guile, if I learn to use guile-gi?
Yes.
For what it's worth I did an attempt to get a minimal GTK app in Python and Guile running (https://gitlab.com/luis-felipe/geteka).
From that exercise, though, I had to choose Python for my current desktop app project, because I found it easier to make progress. But I'd like to try again with Guile knowing what I've learned with Python.
[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1815 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]
next prev parent reply other threads:[~2022-01-16 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 13:37 understanding guile-gi Zelphir Kaltstahl
2022-01-16 16:24 ` Luis Felipe [this message]
2022-01-16 16:45 ` Luis Felipe
2022-01-16 20:39 ` Zelphir Kaltstahl
2022-01-16 21:19 ` Tim Meehan
2022-01-16 21:19 ` Tim Meehan
2022-01-17 2:16 ` Chris Vine
2022-01-17 8:30 ` Zelphir Kaltstahl
2022-01-17 2:08 ` Chris Vine
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='KyQcY4cBaWPTmOn1pDYy67i9ZHpPNE17aWJ8IosFE8UasgIXIS5IF8gepwjjlZXCUl5jp80IC6fPD7ouKmFk_JDy4NxEpzjh_olZqq6G9eM=@protonmail.com' \
--to=luis.felipe.la@protonmail.com \
--cc=guile-user@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/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).