unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: guile-user@gnu.org
Subject: Re: understanding guile-gi
Date: Sun, 16 Jan 2022 20:39:47 +0000	[thread overview]
Message-ID: <adc408ea-1b87-d052-4218-e1c0a3f93798@posteo.de> (raw)
In-Reply-To: <uysNrRY9w0wN6QCTIvc901nsMbLY8rtlK7ElAtZfDvODlNuX5E0x4DzrwKpL0toA3Bp8npucDi9rwdWCsXannHAh15gTYlLjusGLIofvMKg=@protonmail.com>

Thanks for the example link and the explanations! I'll try to learn from the
example.

Best regards,
Zelphir

On 1/16/22 5:45 PM, Luis Felipe wrote:
> On Sunday, January 16th, 2022 at 1:37 PM, Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> wrote:
>
>> 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?).
> Maybe this can serve as an overview of where is everything:
>
> For generic GTK apps (not necessarily targeted at GNOME): https://www.gtk.org/docs/apis/
>
> For GTK apps that integrate well with GNOME: https://developer.gnome.org/documentation/introduction/components.html
>
> Also, for new projects, if you would like your app to adapt well to different screens, like modern web apps do, maybe take a look at libhandy (https://gnome.pages.gitlab.gnome.org/libhandy/) and libadwaita (https://gnome.pages.gitlab.gnome.org/libadwaita/doc/). The latter, if I understand correctly will replace the former.
>
> Also, note that Glade (https://glade.gnome.org/) only supports GTK 3, and there doesn't seem to be any plans to support GTK 4, so people seem to be writing GUIs by hand in GTK 4 projects.

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




  reply	other threads:[~2022-01-16 20:39 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
2022-01-16 16:45 ` Luis Felipe
2022-01-16 20:39   ` Zelphir Kaltstahl [this message]
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=adc408ea-1b87-d052-4218-e1c0a3f93798@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --cc=guile-user@gnu.org \
    --cc=luis.felipe.la@protonmail.com \
    /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).