Rename anaconda to cryptoconda?

[drago01]

On Sat, Dec 1, 2012 at 10:15 PM, Chris Murphy <lists at colorremedies.com> wrote:
>
> On Dec 1, 2012, at 1:10 PM, drago01 <drago01 at gmail.com> wrote:
>>>
>>
>> Well the point seems to be that the partitioning screen isn't really
>> obvious to him .. tbh it is kind of awkward, but it is to late to fix
>> that for F18.
>
> This is why I've stopped all constructive or destructive criticism of anaconda. I find too many UI/UX problems which in the face of many more significant bugs that I feel in comparison that the UI/UX criticisms amount to polish. More serous bugs need to be fixed.
>
> Plus, the UI is changing and has been changing throughout pre-alpha, alpha and pre-beta. This indicates to me that feedback is taken seriously. But it also indicates an ad hoc approach to solving UI/UX problems, rather than having someone particularly skilled with UI/UX vetting the entire design from the outset. What I hope is that the infrastructure changes under the hood make it relatively easy for the whole GUI portion to be completely reconsidered for F19. That was not possible with oldui, it had too many under the hood issues to make significant functional changes.
>
> Now, the OP's example screen shot is quite a good example of inevitably negative UX:
>
> 1. It's 100% text. It hardly constitutes a GUI. Nothing graphical is leveraged to convey the existing or new layouts.
>
> 2. It mixes new install context with previous install contexts, while simultaneously not showing a stitch of partitions by default. Once revealed, the overall partition scheme is obscured by the distribution based organization. Does this really show the same swap twice once for F16 and once for F17 as if there are two swaps? I think Manual Partitioning is trying to do too much and that's where all the confusion comes from and the bugs are creeping in. I also don't have any idea what behaviors are intentional, so I don't know what's a bug and what's just bad design.
>
> 3. The installer should not use conversational tone with the user. It's inherently adversarial. e.g. It is not my f'n fault there are no mount points for F18 yet.
>
> 4. Create new mount points with + icon? And *right below that* are two + icons, neither of which are what this sentence is referring to. The create mount point + icon is actually not in the screen shot, it's far below. But right below, the + symbols that appear are the reveal widgets for F16 and F17. This is confusing.
>
> 5. Why are instructions for the GUI found inside a reveal section for installation? This instruction is making up for non-obvious UI. You'd have to explain how to create a new partition because by default we aren't even looking at partitions, we're looking at distributions. So the + and - icon at the bottom imply add and remove distributions, not partitions.
>
> 6. "Back to destination selection" does not at all convey or imply that settings made in the current section will be discarded, yet that's what happens. Because this button location is unique, and everywhere else in anaconda the button in that location *does* preserve settings, it is completely rational for users to either a.) become confused about whether or not their settings are preserved when clicking this button; or b.) to assume that they are preserved when clicking this button.

Pretty good summary why I think this screen is just a mess from an UI pov.