2019-07-13 19:34:58 +10:00
|
|
|
import QtQuick 2.12
|
|
|
|
|
import QtQuick.Controls 2.12
|
|
|
|
|
import QtQuick.Layouts 1.12
|
|
|
|
|
import "../../Base"
|
|
|
|
|
import "../../utils.js" as Utils
|
|
|
|
|
|
2019-07-14 10:15:20 +10:00
|
|
|
HGridLayout {
|
|
|
|
|
function applyChanges() {
|
2019-07-16 06:14:08 +10:00
|
|
|
if (nameField.changed) {
|
|
|
|
|
saveButton.nameChangeRunning = true
|
2019-07-14 10:15:20 +10:00
|
|
|
|
2019-07-16 06:14:08 +10:00
|
|
|
py.callClientCoro(
|
|
|
|
|
userId, "set_displayname", [nameField.field.text], () => {
|
|
|
|
|
saveButton.nameChangeRunning = false
|
2019-07-25 06:35:38 +10:00
|
|
|
editAccount.headerName =
|
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
|
|
|
Qt.binding(() => accountInfo.display_name)
|
2019-07-16 06:14:08 +10:00
|
|
|
}
|
|
|
|
|
)
|
|
|
|
|
}
|
|
|
|
|
|
2019-07-19 11:58:21 +10:00
|
|
|
if (aliasField.changed) {
|
2019-07-21 22:57:17 +10:00
|
|
|
window.settings.writeAliases[userId] = aliasField.field.text
|
2019-07-19 11:58:21 +10:00
|
|
|
window.settingsChanged()
|
|
|
|
|
}
|
|
|
|
|
|
2019-07-16 06:14:08 +10:00
|
|
|
if (avatar.changed) {
|
|
|
|
|
saveButton.avatarChangeRunning = true
|
2019-07-18 19:18:13 +10:00
|
|
|
let path = Qt.resolvedUrl(avatar.imageUrl).replace(/^file:/, "")
|
2019-07-16 06:14:08 +10:00
|
|
|
|
|
|
|
|
py.callClientCoro(
|
|
|
|
|
userId, "set_avatar_from_file", [path], response => {
|
|
|
|
|
saveButton.avatarChangeRunning = false
|
|
|
|
|
if (response != true) { print(response) }
|
|
|
|
|
}
|
|
|
|
|
)
|
|
|
|
|
}
|
2019-07-14 10:15:20 +10:00
|
|
|
}
|
|
|
|
|
|
2019-07-19 11:58:21 +10:00
|
|
|
function cancelChanges() {
|
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
|
|
|
nameField.field.text = accountInfo.display_name
|
2019-07-19 11:58:21 +10:00
|
|
|
aliasField.field.text = aliasField.currentAlias
|
|
|
|
|
fileDialog.selectedFile = ""
|
|
|
|
|
fileDialog.file = ""
|
2019-07-25 06:35:38 +10:00
|
|
|
|
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
|
|
|
editAccount.headerName = Qt.binding(() => accountInfo.display_name)
|
2019-07-19 11:58:21 +10:00
|
|
|
}
|
|
|
|
|
|
2019-07-14 10:15:20 +10:00
|
|
|
columns: 2
|
2019-07-19 13:59:05 +10:00
|
|
|
flow: pageStack.isWide ? GridLayout.LeftToRight : GridLayout.TopToBottom
|
2019-07-14 10:15:20 +10:00
|
|
|
rowSpacing: currentSpacing
|
|
|
|
|
|
|
|
|
|
Component.onCompleted: nameField.field.forceActiveFocus()
|
|
|
|
|
|
|
|
|
|
HUserAvatar {
|
2019-07-16 06:14:08 +10:00
|
|
|
property bool changed: avatar.imageUrl != avatar.defaultImageUrl
|
|
|
|
|
|
2019-07-14 10:15:20 +10:00
|
|
|
id: avatar
|
|
|
|
|
userId: editAccount.userId
|
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: accountInfo.display_name
|
|
|
|
|
avatarUrl: accountInfo.avatar_url
|
2019-07-16 18:37:39 +10:00
|
|
|
imageUrl: fileDialog.selectedFile || fileDialog.file || defaultImageUrl
|
|
|
|
|
toolTipImageUrl: ""
|
2019-07-14 10:15:20 +10:00
|
|
|
|
|
|
|
|
Layout.alignment: Qt.AlignHCenter
|
|
|
|
|
|
2019-07-16 08:54:21 +10:00
|
|
|
Layout.preferredWidth: Math.min(flickable.height, avatarPreferredSize)
|
2019-07-14 10:15:20 +10:00
|
|
|
Layout.preferredHeight: Layout.preferredWidth
|
2019-07-16 06:14:08 +10:00
|
|
|
|
2019-07-16 10:10:43 +10:00
|
|
|
HRectangle {
|
|
|
|
|
z: 10
|
|
|
|
|
visible: opacity > 0
|
2019-07-16 18:37:39 +10:00
|
|
|
opacity: ! fileDialog.dialog.visible &&
|
|
|
|
|
(! avatar.imageUrl || avatar.hovered) ? 1 : 0
|
2019-07-16 10:10:43 +10:00
|
|
|
|
|
|
|
|
anchors.fill: parent
|
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
|
|
|
color: Utils.hsluv(0, 0, 0,
|
|
|
|
|
(! avatar.imageUrl && overlayHover.hovered) ? 0.9 : 0.7
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
Behavior on opacity { HNumberAnimation {} }
|
|
|
|
|
Behavior on color { HColorAnimation {} }
|
2019-07-16 10:10:43 +10:00
|
|
|
|
|
|
|
|
HColumnLayout {
|
|
|
|
|
anchors.centerIn: parent
|
|
|
|
|
spacing: currentSpacing
|
2019-07-17 01:48:57 +10:00
|
|
|
width: parent.width
|
2019-07-16 10:10:43 +10:00
|
|
|
|
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
|
|
|
HoverHandler { id: overlayHover }
|
|
|
|
|
|
2019-07-16 10:10:43 +10:00
|
|
|
HIcon {
|
2019-07-18 03:40:28 +10:00
|
|
|
svgName: "upload-avatar"
|
2019-07-16 10:10:43 +10:00
|
|
|
dimension: 64
|
|
|
|
|
Layout.alignment: Qt.AlignCenter
|
|
|
|
|
}
|
|
|
|
|
|
2019-07-16 19:29:47 +10:00
|
|
|
Item { Layout.preferredHeight: theme.spacing }
|
2019-07-16 10:10:43 +10:00
|
|
|
|
|
|
|
|
HLabel {
|
|
|
|
|
text: qsTr("Upload profile picture")
|
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
|
|
|
color: (! avatar.imageUrl && overlayHover.hovered) ?
|
|
|
|
|
Qt.lighter(theme.colors.accentText, 1.2) :
|
|
|
|
|
Utils.hsluv(0, 0, 90, 1)
|
|
|
|
|
Behavior on color { HColorAnimation {} }
|
|
|
|
|
|
2019-07-17 01:48:57 +10:00
|
|
|
font.pixelSize: theme.fontSize.big *
|
|
|
|
|
avatar.height / avatarPreferredSize
|
2019-07-16 10:10:43 +10:00
|
|
|
wrapMode: Text.WordWrap
|
2019-07-17 01:48:57 +10:00
|
|
|
horizontalAlignment: Qt.AlignHCenter
|
2019-07-16 19:08:27 +10:00
|
|
|
|
2019-07-16 10:10:43 +10:00
|
|
|
Layout.fillWidth: true
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2019-07-16 06:14:08 +10:00
|
|
|
HFileDialogOpener {
|
|
|
|
|
id: fileDialog
|
|
|
|
|
fileType: HFileDialogOpener.FileType.Images
|
|
|
|
|
dialog.title: qsTr("Select profile picture for %1")
|
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
|
|
|
.arg(accountInfo.display_name)
|
2019-07-16 06:14:08 +10:00
|
|
|
}
|
2019-07-14 10:15:20 +10:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
HColumnLayout {
|
|
|
|
|
id: profileInfo
|
2019-07-16 19:29:47 +10:00
|
|
|
spacing: theme.spacing
|
2019-07-14 10:15:20 +10:00
|
|
|
|
|
|
|
|
HColumnLayout {
|
2019-07-16 19:29:47 +10:00
|
|
|
spacing: theme.spacing
|
2019-07-14 10:15:20 +10:00
|
|
|
Layout.margins: currentSpacing
|
|
|
|
|
|
|
|
|
|
HLabel {
|
|
|
|
|
text: qsTr("User ID:<br>%1")
|
2019-07-16 10:10:43 +10:00
|
|
|
.arg(Utils.coloredNameHtml(userId, userId, userId))
|
2019-07-14 10:15:20 +10:00
|
|
|
textFormat: Text.StyledText
|
|
|
|
|
wrapMode: Text.Wrap
|
|
|
|
|
|
|
|
|
|
Layout.fillWidth: true
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
HLabeledTextField {
|
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
|
|
|
property bool changed: field.text != accountInfo.display_name
|
2019-07-16 06:14:08 +10:00
|
|
|
|
2019-07-25 06:35:38 +10:00
|
|
|
property string fText: field.text
|
|
|
|
|
onFTextChanged: editAccount.headerName = field.text
|
|
|
|
|
|
2019-07-14 10:15:20 +10:00
|
|
|
id: nameField
|
|
|
|
|
label.text: qsTr("Display name:")
|
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
|
|
|
field.text: accountInfo.display_name
|
2019-07-14 10:15:20 +10:00
|
|
|
field.onAccepted: applyChanges()
|
|
|
|
|
|
|
|
|
|
Layout.fillWidth: true
|
|
|
|
|
Layout.maximumWidth: 480
|
|
|
|
|
}
|
2019-07-19 11:58:21 +10:00
|
|
|
|
|
|
|
|
HLabeledTextField {
|
|
|
|
|
property string currentAlias:
|
2019-07-21 22:57:17 +10:00
|
|
|
window.settings.writeAliases[userId] || ""
|
2019-07-19 11:58:21 +10:00
|
|
|
|
|
|
|
|
property bool changed: field.text != currentAlias
|
|
|
|
|
|
|
|
|
|
id: aliasField
|
|
|
|
|
label.text: qsTr("Write alias:")
|
|
|
|
|
field.text: currentAlias
|
|
|
|
|
field.onAccepted: applyChanges()
|
|
|
|
|
|
|
|
|
|
Layout.fillWidth: true
|
|
|
|
|
Layout.maximumWidth: 480
|
|
|
|
|
}
|
2019-07-14 10:15:20 +10:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
HSpacer {}
|
|
|
|
|
|
|
|
|
|
HRowLayout {
|
|
|
|
|
Layout.alignment: Qt.AlignBottom
|
|
|
|
|
|
|
|
|
|
HUIButton {
|
2019-07-16 06:14:08 +10:00
|
|
|
property bool nameChangeRunning: false
|
|
|
|
|
property bool avatarChangeRunning: false
|
|
|
|
|
|
2019-07-14 10:15:20 +10:00
|
|
|
id: saveButton
|
2019-07-19 10:58:38 +10:00
|
|
|
iconName: "apply"
|
|
|
|
|
text: qsTr("Apply")
|
2019-07-16 06:14:08 +10:00
|
|
|
loading: nameChangeRunning || avatarChangeRunning
|
2019-07-19 11:58:21 +10:00
|
|
|
enabled:
|
|
|
|
|
nameField.changed || aliasField.changed || avatar.changed
|
2019-07-14 10:15:20 +10:00
|
|
|
|
|
|
|
|
Layout.fillWidth: true
|
|
|
|
|
Layout.alignment: Qt.AlignBottom
|
|
|
|
|
|
|
|
|
|
onClicked: applyChanges()
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
HUIButton {
|
|
|
|
|
iconName: "cancel"
|
|
|
|
|
text: qsTr("Cancel")
|
2019-07-19 11:58:21 +10:00
|
|
|
enabled: saveButton.enabled && ! saveButton.loading
|
2019-07-14 10:15:20 +10:00
|
|
|
|
|
|
|
|
Layout.fillWidth: true
|
|
|
|
|
Layout.alignment: Qt.AlignBottom
|
|
|
|
|
|
2019-07-19 11:58:21 +10:00
|
|
|
onClicked: cancelChanges()
|
2019-07-14 10:15:20 +10:00
|
|
|
}
|
|
|
|
|
}
|
2019-07-13 19:34:58 +10:00
|
|
|
}
|
|
|
|
|
}
|
