fedoradesign / anaconda Goto Github PK

(copying some notes out of / ‘Visual Redesign 2015/anaconda-redesign-2015-garrett.svg’ )

Choosing a language is important for two main reasons: Firstly, someone using the installer needs to fully understand what they are doing, so it should be in a familiar language. Secondly, some things, such as typing passwords (for wifi and setting an admin password), require proper keyboard input.

A filtered language list is shown based on location. Clicking on additional languages (shown translated to the default selection) would disclose more available languages. If location cannot be determined (such as in the case of not having network available), then a list with the top few most popular languages would be shown, with all the rest below, in the scrollable list.

Something like this:

I think right now Anaconda scales as large as you've got the monitor real estate. It might be good to cap it at a certain resolution, and allow for it to expand from some minimum (maybe 800x600, I think we support that at a minimum). There's a few advantages to this:

• The widgets don't fly apart / space out so much making them sometimes harder to reach or look a bit awkward;
• depending on the driver you're using for your vm, it might help make the window easier to use at a smaller size;
• We can make the banners look a lot nicer by being able to design them to fit a min=>max size range. then they can scale rather than be tiny on big monitors.

(From Garrett's comments in anaconda-redesign-2015_round2.svg)

Would it be possible — or even make sense — to have a backup mechanism here? (Just speculating…) I'd guess people using existing operating systems would probably not have backed up before getting to this step, and losing data is an awful thing. Ideally, there shouldn't be any problem (but I always hear about how resizing is risky, but have never experienced problems myself).

However, a drawback with backing up data is how to handle it. There's a lot of hidden UI with that. This is probably best left to a backup utility in the Live image, or a tool inside the preinstalled OS.

For example, if you have no network connection / your connection requires auth or configuration before it can be activated, you need to fill out network details before you can continue.

We need a way of indicating that on the hub / main menu.

Here's the cheap way I did it in the first round of visuals - basically a big asterisk :-p

Considering that hard drives have become faster, SSDs are quite common now, and most people install from things that are not optical media, there might not be enough time to display banners.

Way back in the day, we did banners in Anaconda primarily because installs were slow. We're talking half-an-hour-or-so slow... sometimes even more, if people did custom package selections or had a slow CD-ROM drive or painfully slow network connection. Now, USB drives, SSDs, and super-fast Internet are all pretty typical.

As banners are static and not interactive, and speed is not as much of a concern as it once was, do banners make sense today? If so, then we should then ask, "Do rotating banners make sense?"

Do we have stats on how long a normal, typical Workstation install is on modern-enough (anything in the past couple of years) hardware? Like, say, how long does it take to install Fedora Workstation on an X230, for example? (I'm not going to reinstall my laptop just to check 😉)

Currently anaconda has an input method switching widget in the upper right corner (see screenshot below.) This is required for a few different types of users - for example, a Japanese user needs to be able to switch between kanji, hiragana, katakana, and romaji input. It's also needed for folks who may be multilingual or otherwise have to cope with multiple languages / layouts. (eg English speaker in a French office and needs to configure wifi with a French password using a French keyboard - as configured by default you can't input even basic acute accents IIRC.)

We need to figure out where / when to display the widget for the folks who need it. At a minimum I think it should be displayed wherever there might be keyboard input.

Right now we don't have any mockups to show what the spoke screens will look like - the main challenge here is placement / treatment of the 'done' button. We can't implement spokes as popups/overlays because they have popups/overlays within them.

We have just the language name but Anaconda has the notion of locale as well, e.g.:

One challenge: not sure that the database that gives us these strings is all that friendly.

Maybe I'm overly conscious about the plight of someone who can't understand English, but...

BEFORE

AFTER

I'm worried about the "Additional languages" item too - is there a good graphical way to represent that?

Minor issue. Need to update artwork with workstation green artwork. ( / ‘Visual Redesign 2015/anaconda-redesign-2015-garrett.svg’ )