From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New packages: libadwaita-qt adwaita-qt-devel
Date: Sat, 10 Apr 2021 13:35:20 +0200 [thread overview]
Message-ID: <20210410113520.mtl9umoSCdImRsU8NsgYn0mSKxG4A8mS0Zb15dKkKhI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30117@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/30117#issuecomment-817122193
Comment:
I see why you named the library libadwaita-qt, but I think it will soon become very confusing for users. [libadwaita](https://gitlab.gnome.org/GNOME/libadwaita/) is a name of a new GNOME library (continuation of libhandy) which will provide GTK4 widgets with the Adwaita design. Naming this package libadwaita-qt makes sense, but I can see why people could be confused by it.
from [Introducing libadwaita](https://adrienplazas.com/blog/2021/03/31/introducing-libadwaita.html):
> Adwaita is the name of GNOME’s visual language and identity, and it is already used by two projects implementing it: the Adwaita GTK stylesheet and the Adwaita icon set. This new libadwaita library intends to extend that concept by being the missing code part of Adwaita. The library will be implemented as a direct GTK 4 continuation and replacement of libhandy, and it will be developed by libhandy’s current developers.
next prev parent reply other threads:[~2021-04-10 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 5:13 [PR PATCH] " phossil
2021-04-10 10:17 ` Chocimier
2021-04-10 11:35 ` paper42 [this message]
2021-04-10 11:51 ` Chocimier
2021-04-10 12:34 ` paper42
2021-04-10 19:44 ` [PR PATCH] [Updated] adwaita-qt: split libadwaita-qt and adwaita-qt-devel phossil
2021-04-12 15:41 ` Chocimier
2022-05-17 2:15 ` github-actions
2022-06-01 2:14 ` [PR PATCH] [Closed]: " github-actions
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210410113520.mtl9umoSCdImRsU8NsgYn0mSKxG4A8mS0Zb15dKkKhI@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).