DTS CE and SE should use similar UX to ChromeOS Firmware Utility

[pietrushnic]

The problem you're addressing (if any)

Current interface is confusing for end users. Explanation of the process which happen on the screen is not user friendly for most members of our community.

Describe the solution you'd like

We should leverage MrChromebox experience implemented in scripts. Please check slides here: https://mrchromebox.tech/#fwscript

We should maybe even hide more advanced options in submenu. We can probably do even better then in mentioned scripts but we should start with something reasonably scalable.

I would expect from person who will implement this feature to really compare UX between DTS CE and MrChromebox Firmware Utility Script.

Where is the value to a user, and who might that user be?

Simpler and more friendly looking interface. Extensible interface for future improvements.

Describe alternatives you've considered

Maybe simple ncurses interface would be better, since sooner or later we will transform into real application. There are also cool things written in Go and working as very nice terminal user interface applications. Of course we cannot go to far since application have to be usable over serial.

Additional context

[macpijan]

Some experiment was done here: #361 (comment)

[pietrushnic]

@macpijan Thanks, I was recalling that discussion, but I was not able to find it. I'm not sure if a GH discussion would have practical use for us. Anyway, it would be great if the topic of UX would be scheduled in DTS.

[macpijan]

Steps to achieve this:

• Move DTS into a separate repo first: Move DTS to a separate repository #773
• Replace code for UI with the one from: https://github.com/Dasharo/dts/blob/v2/src/functions.sh

[DaniilKl]

Replace code for UI with the one from:

@macpijan, the code was merged with DTS here: Dasharo/dts-scripts#2. Does it cover your request? If so, can this issue be closed, or we are planning to continue developing DTS UI?

[macpijan]

Original request was from @pietrushnic but yest - I believe this is solved already.

[pietrushnic]

@macpijan @DaniilKl Yes, I couldn't be more happy to see it implemented after more than 2 years. Thank you.