What came after this was a bit confusing to me, but I want to throw in something I experienced when I was about to design something from scratch. Does this mean that with this release you won't have to re-run the installer? I noticed that you can just resource any config file(s) after writing changes to it, which in my basic interface designs made it automatically update all changes etc. Do I miss something here? That would be great.
Not possible because the current process will not update the function. When you launch obarun-install bash will load function in memory and so if you don't restart the script those function will not updated. That's why you need to start again obarun-install when you udpate it. Note if you only update obarun-install-themes the script will not ask you ask to restart it because this package do not contain loaded function.
This led me to rethink the main menu radically to this
i have a better for you
upload
:lol:
Because yeah, we don't need to touch anything to install the system if your disk is already prepared!
So, it's a little too minimalist. For example where i put the partition menu because it can be optional or not and thus depending of the user choice.
Mouse could be disabled for any dialog. May reduce input options to only keyboard but then again if it causes unexpected behavior it may be a better choice to prevent confusion at the user end
agreed
You offer parted, sfdisk, fdisk and sgdisk as partioning tools for manual formatting. Let's see what each is and does
yes but no. I don't see any real reason to block a choice due of the firmware interface. For example i use gpt table and BIOS firmware and my preferred program is fdisk