Hi dear YaSTies, after thursday UI meeting I spend part of today researching and thinking about our UI and do some brainstorming.
1. TUI use cases Beside known limited serial line and low memory systems, one another well known use case is WSL. We use TUI here for firstboot and on windows there is by default no X server. I think that WUI could really help here. What can be a bit like competition to us just on different level is IPMI and it is nowadays provided by BIOS or by WUI see https://www.thomas-krenn.com/en/wiki/Supermicro_IPMI_Configuration_through_BIOS_or_Web_Interface And BIOS uses TUI. 2. terminal output of autoyast Well, to this idea brings me mentioning of readline and also usage of autoyast for more complex cases. Basically idea is to have just progress output for autoyast + error reporting ( so no semi automatic or stuff like this in autoyast ). And instead of TUI beside gui it can use simple terminal output e.g. using this quite nice library - https://github.com/shopify/cli-ui or tty-progressbar 3. WUI for autoyast config When I am thinking about replacing TUI by WUI and how to start, then I think ideal candidate is autoyast config UI because: a. current state is bad b. it is too much restricted by system where it runs ( e.g. just think about how much UI is affected by system architecture like not showing s390 options or not able to run it at all ) c. its output is just XML file, no system modification d. I have in mind nice use case of hosted autoyast config creator with maybe nice feature of using mksusecd and creating dvd including autoyast profile, that can be auto detected. So you download iso with your preconfigured autoyast profile. e. it is not used in installation 4. drag and drop in ncurses it should be possible as mouse support mouse down and also mouse up. See doc at https://tldp.org/HOWTO/NCURSES-Programming-HOWTO/mouse.html BTW there is also quite nice quick intro to curses at https://www.2n.pl/blog/basics-of-curses-library-in-ruby-make-awesome-terminal-apps Josef -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
