-
Notifications
You must be signed in to change notification settings - Fork 13
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
Unify settings pages components #37
Unify settings pages components #37
Conversation
f167143
to
60c4590
Compare
Goal is to make the use of font and icon size and row heigts consistent over all settings pages. As well as to add a HighlightBar for visual feedback and make all rows clickable like in the settings main list. - Remove PageHeader from Units, Display and Nighstand page - Refactor all display, sound and nightstand value selectors into IntSelector - Refactor nightstand page action button to LabeledActionButton - Refactor all possible instances of switches into LabeledSwitch in Units, Display, Nighstand and Sound page. - Remove margins from flickables so components can use the full screen width for the HighlightBar - Set rowHeight of Dims.h(25) for all clickable rows - Move ListItem component to qml-asteroid for consitency Depends on AsteroidOS/qml-asteroid#37 to add and modify the components. Signed-off-by: Timo Könnecke koennecke@mosushi.de
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few additional suggestions.
Since this adds three new controls, would it make sense to bump the revision to 1.1? |
c906a26
to
71fbaba
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Much cleaner and more elegant. Well done!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work!
Some minor questions / suggestions.
- Bind onClick property to the parent - Bind forceOn property to parent so the PowerPage can enforce highlight to generate radio button beaviour - Use OutQuad easing so that the highlight is visible very fast after onPressed is registered. else it would not be visible on short presses. Co-authored-by: Ed Beroset <beroset@ieee.org> Signed-off-by: Timo Könnecke koennecke@mosushi.de
…ht and Dims.h(25) rowHeight
- Change hardcoded size definitions to global variables that have a sane defaults and can be altered in the component call - Comment all added property variables and alias Thanks to @beroset for help with the comments Co-authored-by: Ed Beroset <beroset@ieee.org> Signed-off-by: Timo Könnecke koennecke@mosushi.de
- revert receiving of functions through the onClicked property, to sending the signal clicked to the parent Co-authored-by: Darrel Griët <dgriet@gmail.com> Signed-off-by: Timo Könnecke koennecke@mosushi.de
78662c3
to
e3b0572
Compare
Unifiy the layouts of the components used on the settings pages to fixed font and icon size.
Give horizontal spacing/margin within the component so the full width of the screen can be used and must not be limited by margins given in the settings pages.