Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Discussion] Requirements for UI rework #346

Open
Wuzzy2 opened this issue Jan 13, 2020 · 0 comments
Open

[Discussion] Requirements for UI rework #346

Wuzzy2 opened this issue Jan 13, 2020 · 0 comments

Comments

@Wuzzy2
Copy link
Member

Wuzzy2 commented Jan 13, 2020

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.

Note: This issue is blocked by #345.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant