GUI #106

New Issue

esavkin · 2024-05-08T15:28:21+08:00

esavkin commented

2024-05-08 15:28:21 +08:00

I raise this issue for a proper discussion of GUI prototyping and development after 2.5 previous attempts. The discussion is needed, because the GUI is intended to be used by more than one person, and thus cannot be tailored to one particular taste - it should satisfy majority of users. Reactive development often leads to GUI, that is developed by majority of open-source projects - well flexible, but making basic tasks requiring too much time/experience from user (best example for this anti-UX is GIMP).

For now we'll need:

Define which problem the GUI needs to solve, who will use it and on what kind of devices
Define user flow
Check if there are already good solutions in the market
Define the visual style - either adopt existing one or create new
Define internal architecture and code layout
Prototype the UI and test with non-developers
Refine successful prototype

I raise this issue for a proper discussion of GUI prototyping and development after 2.5 previous attempts. The discussion is needed, because the GUI is intended to be used by more than one person, and thus cannot be tailored to one particular taste - it should satisfy majority of users. Reactive development often leads to GUI, that is developed by majority of open-source projects - well flexible, but making basic tasks requiring too much time/experience from user (best example for this anti-UX is GIMP). For now we'll need: 1. Define which problem the GUI needs to solve, who will use it and on what kind of devices 2. Define user flow 3. Check if there are already good solutions in the market 4. Define the visual style - either adopt existing one or create new 5. Define internal architecture and code layout 6. Prototype the UI and test with non-developers 7. Refine successful prototype

sb10q commented

2024-05-08 18:41:04 +08:00

Current GUI design is fine. I have used it rather extensively for laser systems. There weren't 2.5 previous attempts at design. There are "just" lots of bugs and code quality problems.

👎 1

sb10q closed this issue

2024-05-08 18:41:04 +08:00

Sign in to join this conversation.

No Label

No Milestone

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: M-Labs/thermostat#106