This issue is to discuss how a possible, proper UI rework could work and what the requirements are.
I suggest that before the UI is reworked again (or the old code is used again), it's better to work out a clear list of requirements and maybe a concrete design and drafts before actually writing any code.
That's to make sure we all sit in the same boat and no ugly surprises happen.
One (technical) requirement I do have is that the new UI must not be done on the master branch. It can be merged back to master once the work is finished, stable and tested.
This issue is to discuss how a possible, proper UI rework could work and what the requirements are.
I suggest that before the UI is reworked again (or the old code is used again), it's better to work out a clear list of requirements and maybe a concrete design and drafts before actually writing any code.
That's to make sure we all sit in the same boat and no ugly surprises happen.
One (technical) requirement I do have is that the new UI must not be done on the
masterbranch. It can be merged back tomasteronce the work is finished, stable and tested.Note: This issue is blocked by #345.