Details
-
Epic
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
None
-
None
Description
What is the benefit? Why is this valuable?
Currently creation of multi-page applications is hard in DS and requires user to know how QML operates. There is no draggable component for new page creation
What are common use cases?
Any application that has multiple screens
Technical information
Needed: QML type which derives the size from the screen resolution defined for the target. Screen also 'knows' what is the user transition effect when this page is opened.
Screen component needs also to be performant. If Screen item should be used to define view layout only. If things like background color for the whole app is changed, it should be in the window itself.
- QQC type 'Page' needs to be there, need a renaming
- MCU calls internal component 'Screen Layer'
- same applies to 'Application'
- MCU calls internal component 'Screen Layer'
First: Concepting first (MCU, MPU usecase, UX for the screen)