You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the 1.0.0 release it would be nice to clean up the API to make it more clear and improve ease of use. Also there are various implementation patterns/concepts that can be improved. For example:
Rename VeQuickItem isValid -> valid to avoid porting errors and inconsistent property naming
Rename ListItem allowed to something else. We want something like visible but named differently (show is less preferable as that sounds like a function). (Or maybe it can be removed altogether?)
Code style:
Review code style and maybe run clang-format and QML equivalent on git commit
Improving UI controls:
Ensure controls always reflect the backend data state. We can show some intermediate state that indicates the control has been pressed, e.g. for toggle switch shows a busy spinner or slides to the middle or such.
Generic improvements:
Some verbose patterns are duplicated (e.g. bottomContentChildren: [ ListLabel { ... } ] combo)
Theme value consolidation - there are way too many values, should use more generic values
Global.dcInputs is used for both input and output services
Have base classes for UI components or models where necessary
Rework OverviewPage to avoid the needs-relayout-retrigger
Use typed properties instead of var everywhere that it is possible. Helps with tooling (e.g. IDE auto-complete) and also possibly a performance improvement when accessing the Global properties.
Utils.js: remove unused functions and move features to C++ where it would be useful
The text was updated successfully, but these errors were encountered:
After the 1.0.0 release it would be nice to clean up the API to make it more clear and improve ease of use. Also there are various implementation patterns/concepts that can be improved. For example:
Larger issues to resolve:
Naming:
ListItem
-derived components are named inconsistently. E.g. we currently have ListNavigationItem, ListAlarm, AlarmLevelRadioButtonGroup. Clean up naming of ListItem-derived types #1760isValid
->valid
to avoid porting errors and inconsistent property namingallowed
to something else. We want something likevisible
but named differently (show
is less preferable as that sounds like a function). (Or maybe it can be removed altogether?)Code style:
Improving UI controls:
Generic improvements:
bottomContentChildren: [ ListLabel { ... } ]
combo)var
everywhere that it is possible. Helps with tooling (e.g. IDE auto-complete) and also possibly a performance improvement when accessing theGlobal
properties.The text was updated successfully, but these errors were encountered: