moment/src/qml/Chat/RoomHeader.qml

139 lines
4.2 KiB
QML
Raw Normal View History

import QtQuick 2.12
import QtQuick.Layouts 1.12
import "../Base"
2019-03-22 14:28:14 +11:00
2019-08-28 12:46:31 +10:00
Rectangle {
property alias buttonsImplicitWidth: viewButtons.implicitWidth
property int buttonsWidth: viewButtons.Layout.preferredWidth
property var activeButton: "members"
property bool collapseButtons:
viewButtons.implicitWidth > width * 0.33 ||
width - viewButtons.implicitWidth <
theme.minimumSupportedWidthPlusSpacing
2019-05-13 03:17:42 +10:00
id: roomHeader
color: theme.chat.roomHeader.background
2019-07-17 07:08:06 +10:00
implicitHeight: theme.baseElementsHeight
2019-03-22 14:28:14 +11:00
HRowLayout {
id: row
2019-07-16 19:29:47 +10:00
spacing: theme.spacing
2019-03-26 09:29:46 +11:00
anchors.fill: parent
2019-03-22 14:28:14 +11:00
HRoomAvatar {
id: avatar
Big performance refactoring & various improvements Instead of passing all sorts of events for the JS to handle and manually add to different data models, we now handle everything we can in Python. For any change, the python models send a sync event with their contents (no more than 4 times per second) to JS, and the QSyncable library's JsonListModel takes care of converting it to a QML ListModel and sending the appropriate signals. The SortFilterProxyModel library is not used anymore, the only case where we need to filter/sort something now is when the user interacts with the "Filter rooms" or "Filter members" fields. These cases are handled by a simple JS function. We now keep separated room and timeline models for different accounts, the previous approach of sharing all the data we could between accounts created a lot of complications (local echoes, decrypted messages replacing others, etc). The users's own account profile changes are now hidden in the timeline. On startup, if all events for a room were only own profile changes, more events will be loaded. Any kind of image format supported by Qt is now handled by the pyotherside image provider, instead of just PNG/JPG. SVGs which previously caused errors are supported as well. The typing members bar paddings/margins are fixed. The behavior of the avatar/"upload a profile picture" overlay is fixed. Config files read from disk are now cached (TODO: make them reloadable again). Pylint is not used anymore because of all its annoying false warnings and lack of understanding for dataclasses, it is replaced by flake8 with a custom config and various plugins. Debug mode is now considered on if the program was compiled with the right option, instead of taking an argument from CLI. When on, C++ will set a flag in the Window QML component. The loading screen is now unloaded after the UI is ready, where previously it just stayed in the background invisible and wasted CPU. The overall refactoring and improvements make us now able to handle rooms with thousand of members and no lazy-loading, where previously everything would freeze and simply scrolling up to load past events in any room would block the UI for a few seconds.
2019-08-11 22:01:22 +10:00
displayName: chatPage.roomInfo.display_name
mxc: chatPage.roomInfo.avatar_url
Layout.alignment: Qt.AlignTop
2019-03-26 09:29:46 +11:00
}
HLabel {
id: roomName
Big performance refactoring & various improvements Instead of passing all sorts of events for the JS to handle and manually add to different data models, we now handle everything we can in Python. For any change, the python models send a sync event with their contents (no more than 4 times per second) to JS, and the QSyncable library's JsonListModel takes care of converting it to a QML ListModel and sending the appropriate signals. The SortFilterProxyModel library is not used anymore, the only case where we need to filter/sort something now is when the user interacts with the "Filter rooms" or "Filter members" fields. These cases are handled by a simple JS function. We now keep separated room and timeline models for different accounts, the previous approach of sharing all the data we could between accounts created a lot of complications (local echoes, decrypted messages replacing others, etc). The users's own account profile changes are now hidden in the timeline. On startup, if all events for a room were only own profile changes, more events will be loaded. Any kind of image format supported by Qt is now handled by the pyotherside image provider, instead of just PNG/JPG. SVGs which previously caused errors are supported as well. The typing members bar paddings/margins are fixed. The behavior of the avatar/"upload a profile picture" overlay is fixed. Config files read from disk are now cached (TODO: make them reloadable again). Pylint is not used anymore because of all its annoying false warnings and lack of understanding for dataclasses, it is replaced by flake8 with a custom config and various plugins. Debug mode is now considered on if the program was compiled with the right option, instead of taking an argument from CLI. When on, C++ will set a flag in the Window QML component. The loading screen is now unloaded after the UI is ready, where previously it just stayed in the background invisible and wasted CPU. The overall refactoring and improvements make us now able to handle rooms with thousand of members and no lazy-loading, where previously everything would freeze and simply scrolling up to load past events in any room would block the UI for a few seconds.
2019-08-11 22:01:22 +10:00
text: chatPage.roomInfo.display_name
font.pixelSize: theme.fontSize.big
color: theme.chat.roomHeader.name
2019-03-26 09:29:46 +11:00
elide: Text.ElideRight
verticalAlignment: Text.AlignVCenter
2019-05-13 03:17:42 +10:00
Layout.fillHeight: true
Layout.maximumWidth: Math.max(
0,
2019-05-17 05:50:14 +10:00
row.width - row.totalSpacing - avatar.width -
2019-05-13 03:17:42 +10:00
viewButtons.width -
(expandButton.visible ? expandButton.width : 0)
)
HoverHandler { id: nameHover }
2019-03-26 09:29:46 +11:00
}
2019-03-22 14:28:14 +11:00
HRichLabel {
id: roomTopic
Big performance refactoring & various improvements Instead of passing all sorts of events for the JS to handle and manually add to different data models, we now handle everything we can in Python. For any change, the python models send a sync event with their contents (no more than 4 times per second) to JS, and the QSyncable library's JsonListModel takes care of converting it to a QML ListModel and sending the appropriate signals. The SortFilterProxyModel library is not used anymore, the only case where we need to filter/sort something now is when the user interacts with the "Filter rooms" or "Filter members" fields. These cases are handled by a simple JS function. We now keep separated room and timeline models for different accounts, the previous approach of sharing all the data we could between accounts created a lot of complications (local echoes, decrypted messages replacing others, etc). The users's own account profile changes are now hidden in the timeline. On startup, if all events for a room were only own profile changes, more events will be loaded. Any kind of image format supported by Qt is now handled by the pyotherside image provider, instead of just PNG/JPG. SVGs which previously caused errors are supported as well. The typing members bar paddings/margins are fixed. The behavior of the avatar/"upload a profile picture" overlay is fixed. Config files read from disk are now cached (TODO: make them reloadable again). Pylint is not used anymore because of all its annoying false warnings and lack of understanding for dataclasses, it is replaced by flake8 with a custom config and various plugins. Debug mode is now considered on if the program was compiled with the right option, instead of taking an argument from CLI. When on, C++ will set a flag in the Window QML component. The loading screen is now unloaded after the UI is ready, where previously it just stayed in the background invisible and wasted CPU. The overall refactoring and improvements make us now able to handle rooms with thousand of members and no lazy-loading, where previously everything would freeze and simply scrolling up to load past events in any room would block the UI for a few seconds.
2019-08-11 22:01:22 +10:00
text: chatPage.roomInfo.topic
textFormat: Text.StyledText
font.pixelSize: theme.fontSize.small
color: theme.chat.roomHeader.topic
2019-03-26 09:29:46 +11:00
elide: Text.ElideRight
verticalAlignment: Text.AlignVCenter
2019-05-13 03:17:42 +10:00
Layout.fillHeight: true
Layout.maximumWidth: Math.max(
0,
row.width - row.totalSpacing - avatar.width -
2019-05-13 03:17:42 +10:00
roomName.width - viewButtons.width -
(expandButton.visible ? expandButton.width : 0)
)
HoverHandler { id: topicHover }
}
HToolTip {
text: name && topic ? (name + "<br>" + topic) : (name || topic)
label.textFormat: Text.StyledText
visible: text && (nameHover.hovered || topicHover.hovered)
readonly property string name:
roomName.truncated ?
("<b>" + chatPage.roomInfo.display_name + "</b>") : ""
readonly property string topic:
roomTopic.truncated ? chatPage.roomInfo.topic : ""
2019-03-22 14:28:14 +11:00
}
2019-03-26 09:29:46 +11:00
2019-04-29 05:22:53 +10:00
HSpacer {}
2019-05-13 03:17:42 +10:00
Row {
id: viewButtons
Layout.preferredWidth: collapseButtons ? 0 : implicitWidth
Layout.fillHeight: true
Repeater {
model: [
"members", "files", "notifications", "history", "settings"
]
2019-08-21 07:41:24 +10:00
HButton {
backgroundColor: "transparent"
icon.name: "room-view-" + modelData
iconItem.dimension: 22
2019-08-21 07:41:24 +10:00
height: parent.height
2019-09-02 10:33:05 +10:00
spacing: theme.spacing / 1.5
topPadding: 0
bottomPadding: topPadding
autoExclusive: true
checked: activeButton == modelData
enabled: modelData == "members"
toolTip.text: qsTr(
modelData.charAt(0).toUpperCase() + modelData.slice(1)
)
2019-08-21 07:41:24 +10:00
onClicked: activeButton =
activeButton == modelData ? null : modelData
}
2019-05-13 03:17:42 +10:00
}
Behavior on Layout.preferredWidth {
HNumberAnimation { id: buttonsAnimation }
2019-05-13 03:17:42 +10:00
}
}
}
2019-08-21 07:41:24 +10:00
HButton {
2019-05-13 03:17:42 +10:00
id: expandButton
z: 1
2019-08-21 07:41:24 +10:00
width: height
height: parent.height
2019-09-02 10:33:05 +10:00
spacing: theme.spacing / 1.5
topPadding: 0
bottomPadding: topPadding
2019-05-13 03:17:42 +10:00
anchors.right: parent.right
opacity: collapseButtons ? 1 : 0
visible: opacity > 0
enabled: false // TODO
2019-08-21 07:41:24 +10:00
backgroundColor: "transparent"
icon.name: "reduced-room-buttons"
2019-05-13 03:17:42 +10:00
Behavior on opacity {
HNumberAnimation { duration: buttonsAnimation.duration * 2 }
2019-05-13 03:17:42 +10:00
}
2019-03-22 14:28:14 +11:00
}
}