From: raingloom <raingloom@riseup.net>
To: guix-devel@gnu.org
Subject: Re: Towards a graphical installer?
Date: Tue, 12 May 2020 04:58:25 +0200 [thread overview]
Message-ID: <20200512045825.6b3ff8b3@riseup.net> (raw)
In-Reply-To: <20200511162909.4shsuvtnbxfyvuv2@pelzflorian.localdomain>
On Mon, 11 May 2020 18:29:09 +0200
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> wrote:
> On Mon, May 11, 2020 at 03:27:29PM +0200, Mathieu Othacehe wrote:
> > A way to move forward with the installer could be to propose an ISO
> > image starting a desktop-environment by default. […]
>
> Thank you for investigating.
>
> I suppose keyboard input method (IME) support is a reason why someone
> might wish to use an Xorg-based installer. Are there other reasons?
> What are the reasons for a real desktop environment; is the goal to
> offer a live image? Previously I would have thought a virtual console
> is more likely to work everywhere, but kmscon has the same
> requirements as Xorg and without kmscon we’d lose i18n.
>
> Regards,
> Florian
>
Can the TUI installer be used with a screen reader? AFAIK it can't but
I'd love to be proven wrong.
Anyway, there are also other accessibility options that are useful. High
contrast, magnifier, sticky keys, etc. GNOME provides these.
Even if you aren't blind or disabled in general, you might just have to
install an operating system without a working screen one day.
next prev parent reply other threads:[~2020-05-12 2:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 13:27 Towards a graphical installer? Mathieu Othacehe
2020-05-11 15:17 ` Jonathan Brielmaier
2020-05-11 16:01 ` Tobias Geerinckx-Rice
2020-05-13 7:11 ` Mathieu Othacehe
2020-05-11 16:29 ` pelzflorian (Florian Pelz)
2020-05-12 2:58 ` raingloom [this message]
2020-05-12 3:49 ` John Soo
2020-05-13 7:20 ` Mathieu Othacehe
2020-05-13 9:28 ` pelzflorian (Florian Pelz)
2020-05-24 20:17 ` Ludovic Courtès
2020-05-11 19:50 ` Pierre Neidhardt
2020-05-11 20:03 ` Leo Famulari
2020-05-11 22:27 ` Christopher Lemmer Webber
2020-05-12 7:09 ` Pierre Neidhardt
2020-05-12 15:33 ` Christopher Lemmer Webber
2020-05-13 5:44 ` dftxbs3e
2020-05-13 7:56 ` Pierre Neidhardt
2020-05-12 6:10 ` dftxbs3e
2020-05-12 6:13 ` dftxbs3e
2020-05-12 20:53 ` hamzeh
2020-05-14 8:08 ` Christopher Baines
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200512045825.6b3ff8b3@riseup.net \
--to=raingloom@riseup.net \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).