Details
-
Epic
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
None
-
None
-
Page creation according to recommendations
Description
What is the benefit? Why is this valuable?
This is needed to guide users to create user interfaces the way we recommend.
What are common use cases?
Any UI creation
Technical information
When user adds component to the form view it becomes part of the currently open UI.QML. This leads to situation that a) pollutes the page and b) does not allow user to add various things to the component (like function calls etc).
Therefore, when user adds a component or functionality which is not something UI.QML allows, we should display a modal dialog and query if user wants to create a component out from this instead. If user says yes, we open the 'move to component' modal in cascaded mode (does not exist yet) where only component name edit field, OK and Cancel are shown. By default the 'ui.qml' button is unchecked too.
Needs:
- Changes to the move to component modal
- put every option apart component name into cascaded view (can be opened by clicking 'advanced' button)
- by default mark 'ui.qml' button off
- Change the error dialog (shown when incompatible UI.QML code is detected) so it tells user that the action he/she is doing is not possible in UI.QML, want to move it to normal QML component instead?