Qt Quick Controls 2.0 chapter

[e8johan]

This is work in progress - do not merge!

I've outlined where to add Qt Quick Controls 2.0 references and a general outline for the main chapter on Qt Quick Controls 2.0 and am looking for feedback.

[mitchcurtis]

Not sure what kind of review you're after at this stage... probably more high-level, I guess, but I pointed out some grammar issues just in case.

[mitchcurtis]

What kind of content did you have planned for this section?

[e8johan]

This is an outline. The contents would answer these questions and introduce the topic.

[mitchcurtis]

Yes, I understand that it's an outline, I'm just curious about what you plan on putting here, on a high level.

[mitchcurtis]

So the "implementation for desktop" part of the example will cover the "How to use them on desktop" section?

[e8johan]

As this is the highlevel introduction, this will be showing how to do something that fits onto a desktop with the controls. E.g. menus and such, and try to contrast that with the next section which will focus more on a device/phone style UI (e.g. one main window vs one document window, stackview vs dialogs, etc).
This will be more of a whirlwind tour, so some code demonstrating the elements and screenshots showing the possibilities. The actual details will be covered more in depth further down.

[mitchcurtis]

I think this should say "Which controls exist". Or maybe "The list of controls" would be better.

[e8johan]

This bullet is more of a placeholder for the contents planned. I want to add a set of paragraphs answering this question.

[mitchcurtis]

What does this mean? What will the content be?

[e8johan]

Same here, the contents is supposed to address these questions.

[mitchcurtis]

What's this one? Do you have an example image/screenshot? Which concrete types would this use?

[e8johan]

These would probably be one sub-section each discussing best practices for setting up these common interaction patterns.

[e8johan]

Good feedback - thanks!

I'm more after high level feedback on the flow. Does the high level story hold (answering all the bullet questions in this order) and have I covered all the key topics?

[mitchcurtis]

Good feedback - thanks!

I'm more after high level feedback on the flow. Does the high level story hold (answering all the bullet questions in this order) and have I covered all the key topics?

I think it looks fine.

Some other things that may be worth mentioning when you get to the content stage:

• Palette support, although not supported for each style yet, might be worth mentioning as the best solution for tweaking colours without overriding whole delegates and hence losing the style.
• The imagine style would be worth mentioning as a designer-friendly solution for creating a style without having to code.

[e8johan]

I introduced this in the Introduction section that I just pushed.

[e8johan]

As this is the highlevel introduction, this will be showing how to do something that fits onto a desktop with the controls. E.g. menus and such, and try to contrast that with the next section which will focus more on a device/phone style UI (e.g. one main window vs one document window, stackview vs dialogs, etc).
This will be more of a whirlwind tour, so some code demonstrating the elements and screenshots showing the possibilities. The actual details will be covered more in depth further down.

[mitchcurtis]

StatusBar is a Controls 1 type, so we should leave it out.

[mitchcurtis]

You could probably use the screenshots from the docs if you wanted. E.g.: https://doc.qt.io/qt-5/qtquickcontrols2-material.html

[e8johan]

That would imply that the CLA applies to the Qt resources, so I'll leave it for now.

[mitchcurtis]

I wonder if we should use the dialogs from Qt.labs.platform instead?

[e8johan]

I wanted a pure QML solution first, since the labs module requires QtWidgets. I've added a note about this, and there is a separate section on the labs module.