Upcoming snacks in Qt Quick
The Qt blog has a review of upcoming innovations in Qt Quck in the upcoming 5.1. In short, they added widget functionality, an analog to QMainWindow and made it possible to use QML in widget projects, albeit in a slightly truncated version. Thus, Qt Quick is ready for application development and on desktops.
We were given almost everything that we used to see in widgets. The first and perhaps most important are the linkers:
What is the actual problem. In widgets, linkers are a handy tool when it comes to resizing the displayed window. before Qt 5.1, similar functionality could also be implemented in QML, but now it has become easier. An example is the code from this article:
Before:
After:
Added several View classes (or how they are there): SplitView, ScrollView and TableView
The last analogue of QTableView and this classic table view, ScrollView is a kind of analogue of QAbstractScrollArea, SplitView is an analogue of QSplitter.
')
Added classic controls:
And given the opportunity to bend as you please, exactly as VIew-ry.
And so we are offered to use all of this:
Well, at least it did not become more difficult, and together with the initial possibilities of qml to remain true to widgets, I already do not see the point
We were given almost everything that we used to see in widgets. The first and perhaps most important are the linkers:
What is the actual problem. In widgets, linkers are a handy tool when it comes to resizing the displayed window. before Qt 5.1, similar functionality could also be implemented in QML, but now it has become easier. An example is the code from this article:
Before:
ToolBar { Row { id: row spacing: 2 anchors.verticalCenter: parent.verticalCenter ToolButton { iconSource: "images/go-previous.png" } ToolButton { iconSource: "images/go-next.png" } } Slider { anchors.left: row.right anchors.leftMargin: 2 anchors.verticalCenter: parent.verticalCenter anchors.right: parent.right } } After:
ToolBar { RowLayout { anchors.fill: parent spacing: 2 ToolButton { iconSource: "images/go-previous.png" } ToolButton { iconSource: "images/go-next.png" } Slider { Layout.fillWidth: true } } } Added several View classes (or how they are there): SplitView, ScrollView and TableView
The last analogue of QTableView and this classic table view, ScrollView is a kind of analogue of QAbstractScrollArea, SplitView is an analogue of QSplitter.
')
Added classic controls:
And given the opportunity to bend as you please, exactly as VIew-ry.
And so we are offered to use all of this:
GroupBox { id: gridBox title: "Grid layout" Layout.fillWidth: true GridLayout { id: gridLayout anchors.fill: parent rows: 3 flow: GridLayout.TopToBottom Label { text: "Line 1" } Label { text: "Line 2" } Label { text: "Line 3" } TextField { } TextField { } TextField { } TextArea { text: "This widget spans over three rows in the GridLayout.\n" + "All items in the GridLayout are implicitly positioned from top to bottom." Layout.rowSpan: 3 Layout.fillHeight: true Layout.fillWidth: true } } } Well, at least it did not become more difficult, and together with the initial possibilities of qml to remain true to widgets, I already do not see the point
Links
Source: https://habr.com/ru/post/184288/
All Articles