Open garrett opened 9 months ago
For context, when you launch Anaconda's Cockpit Storage integration, it looks like this:
This would also be similar to what someone sees on a computer with a blank drive. In many cases, someone would probably just fill the drive with Fedora and skip this step.
However, when someone has multiple disks in Cockpit (like they bought a new disk), I think this is still a UI problem.
We probably want to work on the string for "type" and add a default (secondary) action to the left of the ⋮ menu.
After creating a partition table, we see this:
It might still be a good idea to have a default action of a secondary-styled "Create partition" button in the actions area of that row, as that's the only thing you can do with the free space... Aside from leaving it alone.
I made mockups for this.
The top is when there's free space on a disk. Having nothing on the disk (not even a partition table) would look similar too (although I guess the dialog could even grow a modern GPT / legacy MBR option, or even really just default to GPT as it's 2024).
But in a Anaconda UI sync call, a decision was made to focus on other features... even though this would improve the UX for people using Cockpit Storage in Anaconda.
I had some alternative ideas on how to display it too, but I'd suggest the above mockups.
But, again, it was decided that we have "more important things to work on for now".
When running Anaconda from a VM, I realized that it's not obvious what to do when you have a disk without a partition table.
We probably want to make it obvious that a disk doesn't have a partition table, and we might want to consider having a default action to create a partition table. Additionally, in doing so, we probably do not want present much information (like mount partition) and all if people will usually set up a partition table to create partitions which would then be mounted, instead of the entire disk.
So:
I think this needs discussion and probably also some design-related work.