On 5/12/20 7:21 PM, josef Reidinger wrote:
On Tue, 12 May 2020 17:57:17 +0200
Well, if you throwing around crazy ideas, then for me in qt ideal way to do partitioning is visual one.
For "domestic" systems (let's say two disks with one LVM), you are likely right and some visual approach is the best. But, apart from the obvious problem with ncurses, I'm not so sure how well the visual approach scales beyond the most simple scenarios. For SLE customers it's relatively common to have systems with 10+ disks, multipath, RAID and LVM on top. On one hand, those users often use the ncurses interface, on the other, a visual approach would be harder to manage in such scenarios than something based in tables or similar widgets.
So for crazy idea ideally new widget that is like UML diagram or current device graph visualization. Ideally you should be able to drag and drop various components around do arrange it as you want. This way you have in one place two important things - 1. you still see how your partitioning looks like 2. you can quickly rearrange it without long set of delete/create as now. And details like partition sizes and so on will be in object details.
Along that line, something relatively similar to the current devicegraph (but simpler) could be useful. Using the example data from my previous mail I have prepared this stripped-down version of the devicegraph: https://paste.opensuse.org/view/19211592 Of course, the final version should display more information at first sight (like the size of each device, the mount path of the file systems, etc.). But the main idea I wanted to reflect was having all the disks at a top level and all the "leaf nodes" at the bottom one. That bottom line would include both the file systems and the free spaces in vg0 and in sdc (although I didn't add the free spaces to this first version of the image).
Of course question is what to do with ncurses, where it is not possible.
Yep, we need either a good idea that works in both UIs (qt and ncurses) or a couple of good ideas, one for each UI.
another crazy idea for a more guided approach is approach that use autodesk inventor for mechanical designs. Where basically you define relations and it models how result looks like visually. So if you are fine with result you use it and if not you add another constrain ( like size here, angle there or hard join of parts ). To be honest this approach was very productive and easy to use when I was on high school as you again always see result and if it is not what you want, you always just define what is important for you. So as example run you open partitioner and see current partitioning ( or current proposal ) and want to change it. So you e.g. add LVM and define that you want root partition on it and not /home partition on it and it shows you how it will look like after this constrain...and if you still do not like it, you add another, like encryption on home mount point, or set size of root partition to something different and proposal has to respect new value you set.
An interesting idea to consider for the proposal or as special wizard, likely not so much as a general approach for the partitioner. Thanks for the input! -- Ancor González Sosa YaST Team at SUSE Software Solutions -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org