A little bit of rationale for these issues&solutions: 1. There must be some layout set on the Welcome/Language screen -- English (US). And when user selects his/her language we could add the corresponding layout to the list. But we shouldn't remove the English (US) layout and switch to the new layout (at least without letting the user know with some "warning", so we simply shouldn't). Summed up when we get to the Keyboard spoke for the first time, we should have two layouts there -- English (US) and the one based on the language choice (if it is different from the English (US), of course). 2. There must be some layout set all the time because otherwise the user wouldn't be able to use keyboard (How to interpret pressed keys?). So leaving the Keyboard spoke with no layout in the list and greying out the 'Continue' button on the hub doesn't make sense. 3. On the other hand, I completely agree with Martin that it would be confusing/annoying if the '-' button was greyed out with only one layout in the list. When I get to the screen having only the 'English (US)' layout which I don't want to be there, the first think I will do is trying to remove it (natural reaction on something like "Hey, there's something I don't want/need"). I would consider it stupid if it forced me to add another layout first. Still, if the list is empty, we have to have some layout set for the AddLayout dialog's filtering functionality -- English (US). Altogether I think we should a) put both English (US) and language-based layout to the list; b) let the user remove everything first and then add something else. Obviously, when we have to have some layout set, we shouldn't let the user to return from the Keyboard spoke with an empty list, i.e. we should grey out the 'Back to install summary' button or always add the English (US) if the list is empty when leaving the spoke (that might seem confusing, so +1 for the previous one). These are my opinions, please let me know about yours, so that we can get to some final resolution and adapt the code to it. -- Vratislav Podzimek Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
