Introduce Wizard control

[jarolrod]

Introduces the wizard control which will hold all of the onboarding views. A convenient demo can be found here: onboarding-wizard-demo

The demo shows the following views:

[jarolrod]

updated from 35fad87 -> 3ea53bd

changes:

• rebased over master
• Update imports
• Various tidy ups
• Refactor finished() signal to property finished, check onFinishedChanged to see if we should push the node component

[hebasto]

#103 has been merged, please rebase.

[jarolrod]

updated from 3ea53bd -> b93bb21

Changes:

• rebased
• included progress indicator in demo

[GBKS]

This is great. Do you want feedback on this at the moment?

[jarolrod]

updated from b93bb21 -> caf2ba2

Changes:

• rebased over master to drop dependencies on Add and demo ConnectionSettings and ContinueButton components #101 and Support detail item inside option button #103
• rework demo to take into account that the demo's from Add and demo ConnectionSettings and ContinueButton components #101 and Introduce the StorageOptions component and TextButton control #102 have been removed from their respective branches.

[promag]

2d84aa6

nit, bad indentation.

FWIW I don't recommend this approach of loading. It sounds very simple but has some drawbacks:

• say page X is faulty, then those errors will only show when you reach X
• the component instance will use the loader context when resolving property values, this prevents you from using required properties on each page
• You have to stick to the filename convention, and later you have to rename some in order to add a new page in the middle

Instead, I suggest using loader sourceComponent property.

However, I think we can avoid the Loader, like this:

// Wizard.qml
Page {
    default property alias pages: swipeView.data
   
    contentItem: SwipeView {
    }
}

Then to implement some wizard:

Wizard {
    Page1 {
        someRequiredProperty: someWildExpression
    }
    Page2 {
    }
}

Feel free to discuss or ask for help in slack.

[jarolrod]

will leave this as a follow-up for now because, with this suggestion, the file in which we implement all the views will be huge. We probably need a template for each page of the onboarding views in order to keep it tight

[promag]

2d84aa6

add translation. The arrow should be an icon?

[jarolrod]

will keep for a follow-up until I plot out all the necessary types of buttons, and determine if this should be a custom component or not

[jarolrod]

updated from caf2ba2 to 50b9573

changes:

• incorporate most of @promag suggestions
• split out views from this change, to be opened in a future PR

[hebasto]

This PR needs to be rebased.

[jarolrod]

Updated from 50b9573 to dffb73e, also updated the onboarding-wizard-demo for convenient testing

Changes:

• rebased over master

[shaavan]

Amazing work, @jarolrod!
I shall be posting my review soon.

For now, I would like to bring attention to the problem I noticed, which needs to be addressed.

I experimented with different window sizes, and I noticed that the text from the onboarding 03a page is overflowing onto the 03b page for windows with small vertical height.

onboarding 03b page

I thought its best to bring it to the attention before moving forward with reviewing.

[jarolrod]

@shaavan that's just the demo, the window sizes aren't complete on the rudimentary demo and those pages aren't perfect. Just meant to show that the wizard control works and works for all the use cases required, like subpages.

[shaavan]

Got it! I reckoned that this might be the case, as the pages are in the prototype phase. But I still thought to bring it to the notice, just in case this was an unintended issue.

[hebasto]

ACK dffb73e