|
|
|
# Router selection screen
|
|
|
|
|
|
|
|
- routers represented by cards (google's material design terminology)
|
|
|
|
|
|
|
|
|
|
|
|
Do we need…
|
|
|
|
- router groups? Current model/implementation allows assigning tags and colors to router entries, but no named groups…
|
|
|
|
- search/filtering? it's pretty easy to make, but clutters the interface. How many routers would be there in a common usecase?
|
|
|
|
|
|
|
|
|
|
|
|
# Router config screen
|
|
|
|
|
|
|
|
- tabs for individual routers
|
|
|
|
- router name & color from the selection screen card
|
|
|
|
- drag & drop ordering
|
|
|
|
- sidebar for selecting config categories
|
|
|
|
- indicator of unsaved changes
|
|
|
|
- buttons for commit/reset
|
|
|
|
|
|
|
|
|
|
|
|
|
