unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: guile-user@gnu.org
Subject: understanding guile-gi
Date: Sun, 16 Jan 2022 13:37:02 +0000	[thread overview]
Message-ID: <f58b8502-d64d-d7e0-b9f3-0d3276bfae68@posteo.de> (raw)

Hello Guile Users!

I would like to understand guile-gi better, hopefully at some point I will be
able to create GTK applications using Guile. But perhaps my understanding is
wrong, so I want to ask a few things:

guile-gi – I think this stands for "Guile Gnome(?) Introspection"?

gi – I think this "introspection" part of the name is about inspecting sources
and deriving code from that, to make use of Gnome libraries. Or is it for GTK?

Which things are part of GTK and which things are part of Gnome? Currently my
picture is: GTK contains all the GUI things and Gnome the data things. For
example: GTK might contain some date picker dialog or popup or whatever, but the
datatype for date itself would be part of Gnome. "GDate". As such Gnome provides
a sort of common datatypes basis, which could be used by other frameworks as
well (and maybe is?).

So guile-gi makes use of introspection to give access to Gnome datatypes, or
does it create bindings via FFI for an already existing C code base, which is
the actual introspection for Gnome stuff?

And finally: Is my expectation correct, that I will be able to make GTK
applications using Guile, if I learn to use guile-gi?

Best regards,
Zelphir

-- 
repositories: https://notabug.org/ZelphirKaltstahl




             reply	other threads:[~2022-01-16 13:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-16 13:37 Zelphir Kaltstahl [this message]
2022-01-16 16:24 ` understanding guile-gi Luis Felipe
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=f58b8502-d64d-d7e0-b9f3-0d3276bfae68@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --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).