status-im
/
status-desktop
mirror of https://github.com/status-im/status-desktop.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
status-desktop/ui/app/AppLayouts/Chat/ChatLayout.qml

368 lines
15 KiB
QML
Raw Normal View History

desktop(community-settings): add overview and members settings this is first iteration for: #4938
2022-03-23 15:38:23 +00:00
import QtQuick 2.14
import QtQuick.Controls 2.14
import QtQuick.Layouts 1.14
feat(desktop) Added image function in Style Introduced Style.svg() Style.png() Style.emoji() and Style.icon() in Style.qml. Those should be used to set the source in Images instead of using relative paths. Usage: Image { source: Style.svg("check) .... Also moved all Singletons inside a new "utils" folder and made it a QML module, to use import utils 1.0 instead of relative paths Closes #3678
2021-09-28 15:04:06 +00:00
import utils 1.0
feat: add authentication modal to join commmunity view Users that request access to community that are token permissioned need to authenticate and enter their password, so they can reveal their wallet addresses
2023-03-16 14:10:58 +00:00
import shared.popups 1.0
refactor(desktop/chat) Moving chat to new architecture Closes #3710
2021-10-01 15:58:36 +00:00
import "views"
import "stores"
feat(Community/FinaliseOwnership): Added finalise flow in the app - Button from community column. - Button from community overview. - Updated storybook pages (settings overview related) according to new components requirements. Part of #12174
2023-09-28 10:09:47 +00:00
import AppLayouts.Communities.views 1.0
feat(Communities): Communities folder reorganization - Renamed main `CommunitiesPortal` folder to `Communities`. - Created new `layouts` folder. - Moved layout files from chat to communities. - Created new `helpers` folder. - Moved helpers files from chat to communities. - Moved `controls/community` files from chat to communities `controls`. - Moved `panels/communities` files from chat to communities `panels`. - Moved `popups/community` files from chat to communities `popups`. - Moved `views/community` files from chat to communities `views`. - Moved `CommunityBanner` file from shared to `Communities/controls`. Only used in communities context. - Moved `CommunitySettingsView` and `CommunityColumnView` files from chat to communities `views`. - Moved `PermissionsStore.qml` file to `shared/stores`. - Updated imports. - Updated storybook. Part of #6204
2023-06-23 06:17:04 +00:00
import AppLayouts.Communities.popups 1.0
feat(Community/FinaliseOwnership): Added finalise flow in the app - Button from community column. - Button from community overview. - Updated storybook pages (settings overview related) according to new components requirements. Part of #12174
2023-09-28 10:09:47 +00:00
import AppLayouts.Communities.helpers 1.0
chore: split ChatLayout into a seprate file Preliminary work for the wallet. This way, AppLayout isn,t goign to be huge
2020-05-13 17:27:06 +00:00
feat: introduce first JoinCommunityView for token-gated communities This does a few things: - It integrates with the latest `CommunityTokensMetadata` to access community specific ERC721 token - It changes `ChatLayout` such that it conditionally loads either `ChatView` or `JoinCommunityView`. `JoinCommunityView` has been specifically designed for token-gated communities Here's what works (in terms of token permissions): 1. If a community has token permissions and the the current users is not a member of that community, we show `JoinCommunityView` instead of `ChatView` 2. Any community token permissions of type "Become member" are listed in the `JoinCommunityView` 3. There are different types of token critera a permission can have: ERC20 token, ERC721 token, or ENS (which is also ERC721 but we have a type for that nonetheless) Only ERC20 token balances are checked for the known wallet accounts. This happens every time the known token list has been updated (every 10 min atm). We still need to add balance checks for any ERC721 tokens and ENS. 4. If token permissions are created, updated or deleted by the community owner, the `JoinCommunityView` will update in real-time. You'll also notice that the `Reveal my address and request access` button will be enabled if any of the token permissions are fulfilled (only ERC20 at the time being). Clicking that button will not yet send a request. This will be done in the next step as part of https://github.com/status-im/status-desktop/issues/9761
2023-03-07 16:51:06 +00:00
import AppLayouts.Chat.stores 1.0
feat: New design flows to integrate Revealing addresses... ... when joining Community functionality Closes #11138
2023-07-04 15:11:41 +00:00
import AppLayouts.Wallet.stores 1.0 as WalletStore
feat: introduce first JoinCommunityView for token-gated communities This does a few things: - It integrates with the latest `CommunityTokensMetadata` to access community specific ERC721 token - It changes `ChatLayout` such that it conditionally loads either `ChatView` or `JoinCommunityView`. `JoinCommunityView` has been specifically designed for token-gated communities Here's what works (in terms of token permissions): 1. If a community has token permissions and the the current users is not a member of that community, we show `JoinCommunityView` instead of `ChatView` 2. Any community token permissions of type "Become member" are listed in the `JoinCommunityView` 3. There are different types of token critera a permission can have: ERC20 token, ERC721 token, or ENS (which is also ERC721 but we have a type for that nonetheless) Only ERC20 token balances are checked for the known wallet accounts. This happens every time the known token list has been updated (every 10 min atm). We still need to add balance checks for any ERC721 tokens and ENS. 4. If token permissions are created, updated or deleted by the community owner, the `JoinCommunityView` will update in real-time. You'll also notice that the `Reveal my address and request access` button will be enabled if any of the token permissions are fulfilled (only ERC20 at the time being). Clicking that button will not yet send a request. This will be done in the next step as part of https://github.com/status-im/status-desktop/issues/9761
2023-03-07 16:51:06 +00:00
feat(Community/FinaliseOwnership): Added finalise flow in the app - Button from community column. - Button from community overview. - Updated storybook pages (settings overview related) according to new components requirements. Part of #12174
2023-09-28 10:09:47 +00:00
import StatusQ.Core.Utils 0.1
desktop(community-settings): add overview and members settings this is first iteration for: #4938
2022-03-23 15:38:23 +00:00
StackLayout {
refactor(desktop/chat) Cleaning up views
2021-10-21 22:39:53 +00:00
id: root
fix black border on the splitview
2020-05-27 17:10:50 +00:00
fix: pasting a user's profile link in the ad-hoc chat search ... doesn't work in the community section Extract the `Chat.RootStore` as a toplevel/shared property and pass it down to ChatLayouts, instead of cross referencing it between different components. This was also problematic since the ChatLayouts now live inside a Loader, so it's more appropriate to refer to the `Chat.RootStore` directly, instead of `personalChatLayoutLoader.item.rootStore`, since the `personalChatLayoutLoader.item` might not be visible (due to it being inside a Loader and a StackLayout) or it might even be a different component (`loadingStateComponent` or `errorStateComponent`). This also caused similar problems for other components, such as ActivityCenterPopup or StatusStickersPopup. Fixes #9513
2023-02-09 21:49:36 +00:00
property RootStore rootStore
fix(newChat): fix sending messages in new ad hoc chat with new store Fixes #10523 The problem was that the CreateChatView now uses an isolated Chat RootStore, since we can't be sure if the personal chat section will be loaded yet. To fix that, I created a new store that is only for storing the properties needed for that new chat. That way we are sure that it is created and shared to necessary components.
2023-05-04 18:36:35 +00:00
property var createChatPropertiesStore
fix: pasting a user's profile link in the ad-hoc chat search ... doesn't work in the community section Extract the `Chat.RootStore` as a toplevel/shared property and pass it down to ChatLayouts, instead of cross referencing it between different components. This was also problematic since the ChatLayouts now live inside a Loader, so it's more appropriate to refer to the `Chat.RootStore` directly, instead of `personalChatLayoutLoader.item.rootStore`, since the `personalChatLayoutLoader.item` might not be visible (due to it being inside a Loader and a StackLayout) or it might even be a different component (`loadingStateComponent` or `errorStateComponent`). This also caused similar problems for other components, such as ActivityCenterPopup or StatusStickersPopup. Fixes #9513
2023-02-09 21:49:36 +00:00
readonly property var contactsStore: rootStore.contactsStore
feat: introduce first JoinCommunityView for token-gated communities This does a few things: - It integrates with the latest `CommunityTokensMetadata` to access community specific ERC721 token - It changes `ChatLayout` such that it conditionally loads either `ChatView` or `JoinCommunityView`. `JoinCommunityView` has been specifically designed for token-gated communities Here's what works (in terms of token permissions): 1. If a community has token permissions and the the current users is not a member of that community, we show `JoinCommunityView` instead of `ChatView` 2. Any community token permissions of type "Become member" are listed in the `JoinCommunityView` 3. There are different types of token critera a permission can have: ERC20 token, ERC721 token, or ENS (which is also ERC721 but we have a type for that nonetheless) Only ERC20 token balances are checked for the known wallet accounts. This happens every time the known token list has been updated (every 10 min atm). We still need to add balance checks for any ERC721 tokens and ENS. 4. If token permissions are created, updated or deleted by the community owner, the `JoinCommunityView` will update in real-time. You'll also notice that the `Reveal my address and request access` button will be enabled if any of the token permissions are fulfilled (only ERC20 at the time being). Clicking that button will not yet send a request. This will be done in the next step as part of https://github.com/status-im/status-desktop/issues/9761
2023-03-07 16:51:06 +00:00
readonly property var permissionsStore: rootStore.permissionsStore
feat: Single discord channel import UI flow Closes #12039
2023-09-01 07:58:48 +00:00
property var communitiesStore
feat(desktop/contacts) Improvements in contacts Contacts updates currently in base_bc Closes #4100
2021-11-15 15:15:21 +00:00
fix(@desktop/sections): do not unload chat and communities sections during the switching between the sections
2023-03-17 18:58:07 +00:00
property var sectionItemModel
feat(TransferOwnershipPopup): Updated transfer ownership popup according to new design - Applied new design to transfer ownership popup. - Added support in storybook. - Added navigation to transfer ownership popup from community settings / owner token footer. - Added navigation to transfer ownership popup from community settings / overview. - Linked wallet send modal to the transactions popup with the needed pre-populated data. Closes #12171
2023-09-14 10:02:51 +00:00
property var sendModalPopup
fix(@desktop/sections): do not unload chat and communities sections during the switching between the sections
2023-03-17 18:58:07 +00:00
fix(ChatLayout): fix isPrivileged user by using sectionItemModel
2023-08-30 13:33:23 +00:00
readonly property bool isOwner: sectionItemModel.memberRole === Constants.memberRole.owner
readonly property bool isAdmin: sectionItemModel.memberRole === Constants.memberRole.admin
readonly property bool isTokenMasterOwner: sectionItemModel.memberRole === Constants.memberRole.tokenMaster
readonly property bool isControlNode: sectionItemModel.isControlNode
fix(crash): fix crash about community permissions Fixes #11996
2023-08-28 19:56:03 +00:00
readonly property bool isPrivilegedUser: isControlNode || isOwner || isAdmin || isTokenMasterOwner
feat: disable community settings while in Testnet mode - display an info box when in wallet testnet mode with a CTA to disable it (functionality enabled for production builds only) - the CTA can be tested/seen via OverviewSettingsPanelPage storybook page Closes #11468
2023-07-24 11:31:31 +00:00
property bool communitySettingsDisabled
refactor(ChatLayout): expose emoji and sticker popup properties and signals Prior to this change `ChatLayout` exposed `chatView` which let other components access it, its properties and signals. This is problematic as we need to be able to swap out the `ChatView` with the `JoinCommunityView` for token gated communities, in which case there won't be an instance of `chatView`. This commit ensures that we rely purely on inputs and outputs of the component, without exposing the component instance itself.
2023-03-07 16:34:36 +00:00
property var emojiPopup
property var stickersPopup
signal profileButtonClicked()
signal openAppSearch()
uiux(Chat): ensure chat input gets focus when changing views and channels Fixes #804
2020-09-23 07:28:20 +00:00
feat(Community/FinaliseOwnership): Added finalise flow in the app - Button from community column. - Button from community overview. - Updated storybook pages (settings overview related) according to new components requirements. Part of #12174
2023-09-28 10:09:47 +00:00
// Community transfer ownership related props/signals:
// TODO: Backend integrations:
property bool isPendingOwnershipRequest: false
signal ownershipDeclined()
fix(@desktop/chat): Hide create chat panel when some other menu items are selected Fix #7675
2022-11-21 15:46:41 +00:00
onCurrentIndexChanged: {
Global.closeCreateChatView()
}
feat: introduce first JoinCommunityView for token-gated communities This does a few things: - It integrates with the latest `CommunityTokensMetadata` to access community specific ERC721 token - It changes `ChatLayout` such that it conditionally loads either `ChatView` or `JoinCommunityView`. `JoinCommunityView` has been specifically designed for token-gated communities Here's what works (in terms of token permissions): 1. If a community has token permissions and the the current users is not a member of that community, we show `JoinCommunityView` instead of `ChatView` 2. Any community token permissions of type "Become member" are listed in the `JoinCommunityView` 3. There are different types of token critera a permission can have: ERC20 token, ERC721 token, or ENS (which is also ERC721 but we have a type for that nonetheless) Only ERC20 token balances are checked for the known wallet accounts. This happens every time the known token list has been updated (every 10 min atm). We still need to add balance checks for any ERC721 tokens and ENS. 4. If token permissions are created, updated or deleted by the community owner, the `JoinCommunityView` will update in real-time. You'll also notice that the `Reveal my address and request access` button will be enabled if any of the token permissions are fulfilled (only ERC20 at the time being). Clicking that button will not yet send a request. This will be done in the next step as part of https://github.com/status-im/status-desktop/issues/9761
2023-03-07 16:51:06 +00:00
Loader {
feat: channel permissions Closes: #10996, #10995, #10993, #10997, #9537
2023-06-08 11:01:01 +00:00
id: mainViewLoader
feat: introduce first JoinCommunityView for token-gated communities This does a few things: - It integrates with the latest `CommunityTokensMetadata` to access community specific ERC721 token - It changes `ChatLayout` such that it conditionally loads either `ChatView` or `JoinCommunityView`. `JoinCommunityView` has been specifically designed for token-gated communities Here's what works (in terms of token permissions): 1. If a community has token permissions and the the current users is not a member of that community, we show `JoinCommunityView` instead of `ChatView` 2. Any community token permissions of type "Become member" are listed in the `JoinCommunityView` 3. There are different types of token critera a permission can have: ERC20 token, ERC721 token, or ENS (which is also ERC721 but we have a type for that nonetheless) Only ERC20 token balances are checked for the known wallet accounts. This happens every time the known token list has been updated (every 10 min atm). We still need to add balance checks for any ERC721 tokens and ENS. 4. If token permissions are created, updated or deleted by the community owner, the `JoinCommunityView` will update in real-time. You'll also notice that the `Reveal my address and request access` button will be enabled if any of the token permissions are fulfilled (only ERC20 at the time being). Clicking that button will not yet send a request. This will be done in the next step as part of https://github.com/status-im/status-desktop/issues/9761
2023-03-07 16:51:06 +00:00
readonly property var chatItem: root.rootStore.chatCommunitySectionModule
feat: info msg if owner is not awailable after community ownership change (#12560) feat: info msg if the owner is not available after community ownership change
2023-10-31 17:55:41 +00:00
sourceComponent: {
if (chatItem.isCommunity() && !chatItem.amIMember) {
if (chatItem.isWaitingOnNewCommunityOwnerToConfirmRequestToRejoin) {
return controlNodeOfflineComponent
} else if (chatItem.requiresTokenPermissionToJoin) {
return joinCommunityViewComponent
}
}
return chatViewComponent
}
feat: introduce first JoinCommunityView for token-gated communities This does a few things: - It integrates with the latest `CommunityTokensMetadata` to access community specific ERC721 token - It changes `ChatLayout` such that it conditionally loads either `ChatView` or `JoinCommunityView`. `JoinCommunityView` has been specifically designed for token-gated communities Here's what works (in terms of token permissions): 1. If a community has token permissions and the the current users is not a member of that community, we show `JoinCommunityView` instead of `ChatView` 2. Any community token permissions of type "Become member" are listed in the `JoinCommunityView` 3. There are different types of token critera a permission can have: ERC20 token, ERC721 token, or ENS (which is also ERC721 but we have a type for that nonetheless) Only ERC20 token balances are checked for the known wallet accounts. This happens every time the known token list has been updated (every 10 min atm). We still need to add balance checks for any ERC721 tokens and ENS. 4. If token permissions are created, updated or deleted by the community owner, the `JoinCommunityView` will update in real-time. You'll also notice that the `Reveal my address and request access` button will be enabled if any of the token permissions are fulfilled (only ERC20 at the time being). Clicking that button will not yet send a request. This will be done in the next step as part of https://github.com/status-im/status-desktop/issues/9761
2023-03-07 16:51:06 +00:00
}
feat(chat): Removing dynamic scoping from chat section Closes #4244
2022-05-10 16:04:25 +00:00
feat: introduce first JoinCommunityView for token-gated communities This does a few things: - It integrates with the latest `CommunityTokensMetadata` to access community specific ERC721 token - It changes `ChatLayout` such that it conditionally loads either `ChatView` or `JoinCommunityView`. `JoinCommunityView` has been specifically designed for token-gated communities Here's what works (in terms of token permissions): 1. If a community has token permissions and the the current users is not a member of that community, we show `JoinCommunityView` instead of `ChatView` 2. Any community token permissions of type "Become member" are listed in the `JoinCommunityView` 3. There are different types of token critera a permission can have: ERC20 token, ERC721 token, or ENS (which is also ERC721 but we have a type for that nonetheless) Only ERC20 token balances are checked for the known wallet accounts. This happens every time the known token list has been updated (every 10 min atm). We still need to add balance checks for any ERC721 tokens and ENS. 4. If token permissions are created, updated or deleted by the community owner, the `JoinCommunityView` will update in real-time. You'll also notice that the `Reveal my address and request access` button will be enabled if any of the token permissions are fulfilled (only ERC20 at the time being). Clicking that button will not yet send a request. This will be done in the next step as part of https://github.com/status-im/status-desktop/issues/9761
2023-03-07 16:51:06 +00:00
Component {
id: joinCommunityViewComponent
JoinCommunityView {
id: joinCommunityView
fix(@desktop/sections): do not unload chat and communities sections during the switching between the sections
2023-03-17 18:58:07 +00:00
readonly property var communityData: sectionItemModel
feat: channel permissions Closes: #10996, #10995, #10993, #10997, #9537
2023-06-08 11:01:01 +00:00
readonly property string communityId: communityData.id
feat: introduce first JoinCommunityView for token-gated communities This does a few things: - It integrates with the latest `CommunityTokensMetadata` to access community specific ERC721 token - It changes `ChatLayout` such that it conditionally loads either `ChatView` or `JoinCommunityView`. `JoinCommunityView` has been specifically designed for token-gated communities Here's what works (in terms of token permissions): 1. If a community has token permissions and the the current users is not a member of that community, we show `JoinCommunityView` instead of `ChatView` 2. Any community token permissions of type "Become member" are listed in the `JoinCommunityView` 3. There are different types of token critera a permission can have: ERC20 token, ERC721 token, or ENS (which is also ERC721 but we have a type for that nonetheless) Only ERC20 token balances are checked for the known wallet accounts. This happens every time the known token list has been updated (every 10 min atm). We still need to add balance checks for any ERC721 tokens and ENS. 4. If token permissions are created, updated or deleted by the community owner, the `JoinCommunityView` will update in real-time. You'll also notice that the `Reveal my address and request access` button will be enabled if any of the token permissions are fulfilled (only ERC20 at the time being). Clicking that button will not yet send a request. This will be done in the next step as part of https://github.com/status-im/status-desktop/issues/9761
2023-03-07 16:51:06 +00:00
name: communityData.name
fix: community context menu should not say "Leave community" if not joined - differentiate between "Close" and "Leave" a community where the former applies to spectated communities - move the "leave community" confirmation popup to a shared place (Popups.qml), extend it with the outro message and reuse it everywhere - don't let admins leave a community - some minor cleanups and dead code removals Fixes #10963
2023-06-14 08:42:52 +00:00
introMessage: communityData.introMessage
feat: introduce first JoinCommunityView for token-gated communities This does a few things: - It integrates with the latest `CommunityTokensMetadata` to access community specific ERC721 token - It changes `ChatLayout` such that it conditionally loads either `ChatView` or `JoinCommunityView`. `JoinCommunityView` has been specifically designed for token-gated communities Here's what works (in terms of token permissions): 1. If a community has token permissions and the the current users is not a member of that community, we show `JoinCommunityView` instead of `ChatView` 2. Any community token permissions of type "Become member" are listed in the `JoinCommunityView` 3. There are different types of token critera a permission can have: ERC20 token, ERC721 token, or ENS (which is also ERC721 but we have a type for that nonetheless) Only ERC20 token balances are checked for the known wallet accounts. This happens every time the known token list has been updated (every 10 min atm). We still need to add balance checks for any ERC721 tokens and ENS. 4. If token permissions are created, updated or deleted by the community owner, the `JoinCommunityView` will update in real-time. You'll also notice that the `Reveal my address and request access` button will be enabled if any of the token permissions are fulfilled (only ERC20 at the time being). Clicking that button will not yet send a request. This will be done in the next step as part of https://github.com/status-im/status-desktop/issues/9761
2023-03-07 16:51:06 +00:00
communityDesc: communityData.description
color: communityData.color
image: communityData.image
membersCount: communityData.members.count
accessType: communityData.access
joinCommunity: true
feat(@desktop/community): Community admin permissions (#10909) * chore: - replaced admin bool to memberRole - activate admin permissions - configured admin restrictions
2023-06-14 16:00:41 +00:00
amISectionAdmin: communityData.memberRole === Constants.memberRole.owner ||
feat: owner and token master permissions (#11942)
2023-08-22 18:09:34 +00:00
communityData.memberRole === Constants.memberRole.admin ||
communityData.memberRole === Constants.memberRole.tokenMaster
feat: introduce first JoinCommunityView for token-gated communities This does a few things: - It integrates with the latest `CommunityTokensMetadata` to access community specific ERC721 token - It changes `ChatLayout` such that it conditionally loads either `ChatView` or `JoinCommunityView`. `JoinCommunityView` has been specifically designed for token-gated communities Here's what works (in terms of token permissions): 1. If a community has token permissions and the the current users is not a member of that community, we show `JoinCommunityView` instead of `ChatView` 2. Any community token permissions of type "Become member" are listed in the `JoinCommunityView` 3. There are different types of token critera a permission can have: ERC20 token, ERC721 token, or ENS (which is also ERC721 but we have a type for that nonetheless) Only ERC20 token balances are checked for the known wallet accounts. This happens every time the known token list has been updated (every 10 min atm). We still need to add balance checks for any ERC721 tokens and ENS. 4. If token permissions are created, updated or deleted by the community owner, the `JoinCommunityView` will update in real-time. You'll also notice that the `Reveal my address and request access` button will be enabled if any of the token permissions are fulfilled (only ERC20 at the time being). Clicking that button will not yet send a request. This will be done in the next step as part of https://github.com/status-im/status-desktop/issues/9761
2023-03-07 16:51:06 +00:00
communityItemsModel: root.rootStore.communityItemsModel
requirementsMet: root.permissionsStore.allTokenRequirementsMet
feat(communities): add check permissions pending state closes: #11157
2023-08-04 13:14:06 +00:00
requirementsCheckPending: root.rootStore.permissionsCheckOngoing
feat: channel permissions Closes: #10996, #10995, #10993, #10997, #9537
2023-06-08 11:01:01 +00:00
requiresRequest: !communityData.amIMember
communityHoldingsModel: root.permissionsStore.becomeMemberPermissionsModel
viewOnlyHoldingsModel: root.permissionsStore.viewOnlyPermissionsModel
viewAndPostHoldingsModel: root.permissionsStore.viewAndPostPermissionsModel
feat: introduce first JoinCommunityView for token-gated communities This does a few things: - It integrates with the latest `CommunityTokensMetadata` to access community specific ERC721 token - It changes `ChatLayout` such that it conditionally loads either `ChatView` or `JoinCommunityView`. `JoinCommunityView` has been specifically designed for token-gated communities Here's what works (in terms of token permissions): 1. If a community has token permissions and the the current users is not a member of that community, we show `JoinCommunityView` instead of `ChatView` 2. Any community token permissions of type "Become member" are listed in the `JoinCommunityView` 3. There are different types of token critera a permission can have: ERC20 token, ERC721 token, or ENS (which is also ERC721 but we have a type for that nonetheless) Only ERC20 token balances are checked for the known wallet accounts. This happens every time the known token list has been updated (every 10 min atm). We still need to add balance checks for any ERC721 tokens and ENS. 4. If token permissions are created, updated or deleted by the community owner, the `JoinCommunityView` will update in real-time. You'll also notice that the `Reveal my address and request access` button will be enabled if any of the token permissions are fulfilled (only ERC20 at the time being). Clicking that button will not yet send a request. This will be done in the next step as part of https://github.com/status-im/status-desktop/issues/9761
2023-03-07 16:51:06 +00:00
assetsModel: root.rootStore.assetsModel
collectiblesModel: root.rootStore.collectiblesModel
token-permissions: implement the UI "edit" flow for shared addresses Fixes #11599
2023-08-02 17:39:42 +00:00
isInvitationPending: root.rootStore.isCommunityRequestPending(communityId)
fix(JoinCommunityView): Enable activity centre and disable start chat button
2023-03-21 10:54:47 +00:00
notificationCount: activityCenterStore.unreadNotificationsCount
hasUnseenNotifications: activityCenterStore.hasUnseenNotifications
openCreateChat: rootStore.openCreateChat
fix(JoinCommunityView): Change Reveal Address button icon based on auth type
2023-03-30 09:42:28 +00:00
loginType: root.rootStore.loginType
fix(JoinCommunityView): Enable activity centre and disable start chat button
2023-03-21 10:54:47 +00:00
onNotificationButtonClicked: Global.openActivityCenterPopup()
onAdHocChatButtonClicked: rootStore.openCloseCreateChatView()
feat: channel permissions Closes: #10996, #10995, #10993, #10997, #9537
2023-06-08 11:01:01 +00:00
onRevealAddressClicked: {
Global.openPopup(communityIntroDialogPopup, {
token-permissions: implement the UI "edit" flow for shared addresses Fixes #11599
2023-08-02 17:39:42 +00:00
communityId: joinCommunityView.communityId,
feat: channel permissions Closes: #10996, #10995, #10993, #10997, #9537
2023-06-08 11:01:01 +00:00
isInvitationPending: joinCommunityView.isInvitationPending,
name: communityData.name,
introMessage: communityData.introMessage,
imageSrc: communityData.image,
accessType: communityData.access
})
fix: community context menu should not say "Leave community" if not joined - differentiate between "Close" and "Leave" a community where the former applies to spectated communities - move the "leave community" confirmation popup to a shared place (Popups.qml), extend it with the outro message and reuse it everywhere - don't let admins leave a community - some minor cleanups and dead code removals Fixes #10963
2023-06-14 08:42:52 +00:00
}
feat: channel permissions Closes: #10996, #10995, #10993, #10997, #9537
2023-06-08 11:01:01 +00:00
onInvitationPendingClicked: {
token-permissions: implement the UI "edit" flow for shared addresses Fixes #11599
2023-08-02 17:39:42 +00:00
root.rootStore.cancelPendingRequest(communityId)
joinCommunityView.isInvitationPending = root.rootStore.isCommunityRequestPending(communityId)
fix: community context menu should not say "Leave community" if not joined - differentiate between "Close" and "Leave" a community where the former applies to spectated communities - move the "leave community" confirmation popup to a shared place (Popups.qml), extend it with the outro message and reuse it everywhere - don't let admins leave a community - some minor cleanups and dead code removals Fixes #10963
2023-06-14 08:42:52 +00:00
}
feat: introduce first JoinCommunityView for token-gated communities This does a few things: - It integrates with the latest `CommunityTokensMetadata` to access community specific ERC721 token - It changes `ChatLayout` such that it conditionally loads either `ChatView` or `JoinCommunityView`. `JoinCommunityView` has been specifically designed for token-gated communities Here's what works (in terms of token permissions): 1. If a community has token permissions and the the current users is not a member of that community, we show `JoinCommunityView` instead of `ChatView` 2. Any community token permissions of type "Become member" are listed in the `JoinCommunityView` 3. There are different types of token critera a permission can have: ERC20 token, ERC721 token, or ENS (which is also ERC721 but we have a type for that nonetheless) Only ERC20 token balances are checked for the known wallet accounts. This happens every time the known token list has been updated (every 10 min atm). We still need to add balance checks for any ERC721 tokens and ENS. 4. If token permissions are created, updated or deleted by the community owner, the `JoinCommunityView` will update in real-time. You'll also notice that the `Reveal my address and request access` button will be enabled if any of the token permissions are fulfilled (only ERC20 at the time being). Clicking that button will not yet send a request. This will be done in the next step as part of https://github.com/status-im/status-desktop/issues/9761
2023-03-07 16:51:06 +00:00
Connections {
target: root.rootStore.communitiesModuleInst
function onCommunityAccessRequested(communityId: string) {
token-permissions: implement the UI "edit" flow for shared addresses Fixes #11599
2023-08-02 17:39:42 +00:00
if (communityId === joinCommunityView.communityId) {
joinCommunityView.isInvitationPending = root.rootStore.isCommunityRequestPending(communityId)
feat: introduce first JoinCommunityView for token-gated communities This does a few things: - It integrates with the latest `CommunityTokensMetadata` to access community specific ERC721 token - It changes `ChatLayout` such that it conditionally loads either `ChatView` or `JoinCommunityView`. `JoinCommunityView` has been specifically designed for token-gated communities Here's what works (in terms of token permissions): 1. If a community has token permissions and the the current users is not a member of that community, we show `JoinCommunityView` instead of `ChatView` 2. Any community token permissions of type "Become member" are listed in the `JoinCommunityView` 3. There are different types of token critera a permission can have: ERC20 token, ERC721 token, or ENS (which is also ERC721 but we have a type for that nonetheless) Only ERC20 token balances are checked for the known wallet accounts. This happens every time the known token list has been updated (every 10 min atm). We still need to add balance checks for any ERC721 tokens and ENS. 4. If token permissions are created, updated or deleted by the community owner, the `JoinCommunityView` will update in real-time. You'll also notice that the `Reveal my address and request access` button will be enabled if any of the token permissions are fulfilled (only ERC20 at the time being). Clicking that button will not yet send a request. This will be done in the next step as part of https://github.com/status-im/status-desktop/issues/9761
2023-03-07 16:51:06 +00:00
}
}
}
refactor(ChatLayout): expose emoji and sticker popup properties and signals Prior to this change `ChatLayout` exposed `chatView` which let other components access it, its properties and signals. This is problematic as we need to be able to swap out the `ChatView` with the `JoinCommunityView` for token gated communities, in which case there won't be an instance of `chatView`. This commit ensures that we rely purely on inputs and outputs of the component, without exposing the component instance itself.
2023-03-07 16:34:36 +00:00
}
feat: introduce first JoinCommunityView for token-gated communities This does a few things: - It integrates with the latest `CommunityTokensMetadata` to access community specific ERC721 token - It changes `ChatLayout` such that it conditionally loads either `ChatView` or `JoinCommunityView`. `JoinCommunityView` has been specifically designed for token-gated communities Here's what works (in terms of token permissions): 1. If a community has token permissions and the the current users is not a member of that community, we show `JoinCommunityView` instead of `ChatView` 2. Any community token permissions of type "Become member" are listed in the `JoinCommunityView` 3. There are different types of token critera a permission can have: ERC20 token, ERC721 token, or ENS (which is also ERC721 but we have a type for that nonetheless) Only ERC20 token balances are checked for the known wallet accounts. This happens every time the known token list has been updated (every 10 min atm). We still need to add balance checks for any ERC721 tokens and ENS. 4. If token permissions are created, updated or deleted by the community owner, the `JoinCommunityView` will update in real-time. You'll also notice that the `Reveal my address and request access` button will be enabled if any of the token permissions are fulfilled (only ERC20 at the time being). Clicking that button will not yet send a request. This will be done in the next step as part of https://github.com/status-im/status-desktop/issues/9761
2023-03-07 16:51:06 +00:00
}
Component {
id: chatViewComponent
ChatView {
id: chatView
feat: channel permissions Closes: #10996, #10995, #10993, #10997, #9537
2023-06-08 11:01:01 +00:00
readonly property var chatItem: root.rootStore.chatCommunitySectionModule
readonly property string communityId: root.sectionItemModel.id
feat: introduce first JoinCommunityView for token-gated communities This does a few things: - It integrates with the latest `CommunityTokensMetadata` to access community specific ERC721 token - It changes `ChatLayout` such that it conditionally loads either `ChatView` or `JoinCommunityView`. `JoinCommunityView` has been specifically designed for token-gated communities Here's what works (in terms of token permissions): 1. If a community has token permissions and the the current users is not a member of that community, we show `JoinCommunityView` instead of `ChatView` 2. Any community token permissions of type "Become member" are listed in the `JoinCommunityView` 3. There are different types of token critera a permission can have: ERC20 token, ERC721 token, or ENS (which is also ERC721 but we have a type for that nonetheless) Only ERC20 token balances are checked for the known wallet accounts. This happens every time the known token list has been updated (every 10 min atm). We still need to add balance checks for any ERC721 tokens and ENS. 4. If token permissions are created, updated or deleted by the community owner, the `JoinCommunityView` will update in real-time. You'll also notice that the `Reveal my address and request access` button will be enabled if any of the token permissions are fulfilled (only ERC20 at the time being). Clicking that button will not yet send a request. This will be done in the next step as part of https://github.com/status-im/status-desktop/issues/9761
2023-03-07 16:51:06 +00:00
emojiPopup: root.emojiPopup
stickersPopup: root.stickersPopup
contactsStore: root.contactsStore
rootStore: root.rootStore
fix(newChat): fix sending messages in new ad hoc chat with new store Fixes #10523 The problem was that the CreateChatView now uses an isolated Chat RootStore, since we can't be sure if the personal chat section will be loaded yet. To fix that, I created a new store that is only for storing the properties needed for that new chat. That way we are sure that it is created and shared to necessary components.
2023-05-04 18:36:35 +00:00
createChatPropertiesStore: root.createChatPropertiesStore
feat: Single discord channel import UI flow Closes #12039
2023-09-01 07:58:48 +00:00
communitiesStore: root.communitiesStore
fix(@desktop/sections): do not unload chat and communities sections during the switching between the sections
2023-03-17 18:58:07 +00:00
sectionItemModel: root.sectionItemModel
feat: channel permissions Closes: #10996, #10995, #10993, #10997, #9537
2023-06-08 11:01:01 +00:00
amIMember: chatItem.amIMember
amISectionAdmin: root.sectionItemModel.memberRole === Constants.memberRole.owner ||
feat: owner and token master permissions (#11942)
2023-08-22 18:09:34 +00:00
root.sectionItemModel.memberRole === Constants.memberRole.admin ||
root.sectionItemModel.memberRole === Constants.memberRole.tokenMaster
feat: channel permissions Closes: #10996, #10995, #10993, #10997, #9537
2023-06-08 11:01:01 +00:00
hasViewOnlyPermissions: root.permissionsStore.viewOnlyPermissionsModel.count > 0
hasViewAndPostPermissions: root.permissionsStore.viewAndPostPermissionsModel.count > 0
viewOnlyPermissionsModel: root.permissionsStore.viewOnlyPermissionsModel
viewAndPostPermissionsModel: root.permissionsStore.viewAndPostPermissionsModel
assetsModel: root.rootStore.assetsModel
collectiblesModel: root.rootStore.collectiblesModel
feat(Settings/Communities): implement new communities list Closes #11145
2023-06-21 20:37:51 +00:00
isInvitationPending: root.rootStore.isCommunityRequestPending(chatView.communityId)
feat: introduce first JoinCommunityView for token-gated communities This does a few things: - It integrates with the latest `CommunityTokensMetadata` to access community specific ERC721 token - It changes `ChatLayout` such that it conditionally loads either `ChatView` or `JoinCommunityView`. `JoinCommunityView` has been specifically designed for token-gated communities Here's what works (in terms of token permissions): 1. If a community has token permissions and the the current users is not a member of that community, we show `JoinCommunityView` instead of `ChatView` 2. Any community token permissions of type "Become member" are listed in the `JoinCommunityView` 3. There are different types of token critera a permission can have: ERC20 token, ERC721 token, or ENS (which is also ERC721 but we have a type for that nonetheless) Only ERC20 token balances are checked for the known wallet accounts. This happens every time the known token list has been updated (every 10 min atm). We still need to add balance checks for any ERC721 tokens and ENS. 4. If token permissions are created, updated or deleted by the community owner, the `JoinCommunityView` will update in real-time. You'll also notice that the `Reveal my address and request access` button will be enabled if any of the token permissions are fulfilled (only ERC20 at the time being). Clicking that button will not yet send a request. This will be done in the next step as part of https://github.com/status-im/status-desktop/issues/9761
2023-03-07 16:51:06 +00:00
feat(Community/FinaliseOwnership): Added finalise flow in the app - Button from community column. - Button from community overview. - Updated storybook pages (settings overview related) according to new components requirements. Part of #12174
2023-09-28 10:09:47 +00:00
finaliseOwnershipTransferPopup: finaliseOwnershipPopup
isPendingOwnershipRequest: root.isPendingOwnershipRequest
feat: introduce first JoinCommunityView for token-gated communities This does a few things: - It integrates with the latest `CommunityTokensMetadata` to access community specific ERC721 token - It changes `ChatLayout` such that it conditionally loads either `ChatView` or `JoinCommunityView`. `JoinCommunityView` has been specifically designed for token-gated communities Here's what works (in terms of token permissions): 1. If a community has token permissions and the the current users is not a member of that community, we show `JoinCommunityView` instead of `ChatView` 2. Any community token permissions of type "Become member" are listed in the `JoinCommunityView` 3. There are different types of token critera a permission can have: ERC20 token, ERC721 token, or ENS (which is also ERC721 but we have a type for that nonetheless) Only ERC20 token balances are checked for the known wallet accounts. This happens every time the known token list has been updated (every 10 min atm). We still need to add balance checks for any ERC721 tokens and ENS. 4. If token permissions are created, updated or deleted by the community owner, the `JoinCommunityView` will update in real-time. You'll also notice that the `Reveal my address and request access` button will be enabled if any of the token permissions are fulfilled (only ERC20 at the time being). Clicking that button will not yet send a request. This will be done in the next step as part of https://github.com/status-im/status-desktop/issues/9761
2023-03-07 16:51:06 +00:00
onCommunityInfoButtonClicked: root.currentIndex = 1
onCommunityManageButtonClicked: root.currentIndex = 1
onProfileButtonClicked: {
root.profileButtonClicked()
}
onOpenAppSearch: {
root.openAppSearch()
}
feat: channel permissions Closes: #10996, #10995, #10993, #10997, #9537
2023-06-08 11:01:01 +00:00
onRevealAddressClicked: {
Global.openPopup(communityIntroDialogPopup, {
feat(Settings/Communities): implement new communities list Closes #11145
2023-06-21 20:37:51 +00:00
communityId: chatView.communityId,
isInvitationPending: root.rootStore.isCommunityRequestPending(chatView.communityId),
feat: channel permissions Closes: #10996, #10995, #10993, #10997, #9537
2023-06-08 11:01:01 +00:00
name: root.sectionItemModel.name,
introMessage: root.sectionItemModel.introMessage,
imageSrc: root.sectionItemModel.image,
accessType: root.sectionItemModel.access
})
}
onInvitationPendingClicked: {
feat(Settings/Communities): implement new communities list Closes #11145
2023-06-21 20:37:51 +00:00
root.rootStore.cancelPendingRequest(chatView.communityId)
chatView.isInvitationPending = root.rootStore.isCommunityRequestPending(chatView.communityId)
feat: channel permissions Closes: #10996, #10995, #10993, #10997, #9537
2023-06-08 11:01:01 +00:00
}
refactor(ChatLayout): expose emoji and sticker popup properties and signals Prior to this change `ChatLayout` exposed `chatView` which let other components access it, its properties and signals. This is problematic as we need to be able to swap out the `ChatView` with the `JoinCommunityView` for token gated communities, in which case there won't be an instance of `chatView`. This commit ensures that we rely purely on inputs and outputs of the component, without exposing the component instance itself.
2023-03-07 16:34:36 +00:00
}
refactor(online-users): adding online users for chat/channel
2021-11-30 14:49:45 +00:00
}
desktop(community-settings): add overview and members settings this is first iteration for: #4938
2022-03-23 15:38:23 +00:00
Loader {
fix(MembershipRequests): Remove MembershipRequestsPopup and set-up the navigation to CommunityMembersSettingsPanel Part of https://github.com/status-im/status-desktop/issues/9912
2023-04-06 11:11:57 +00:00
id: communitySettingsLoader
fix(crash): fix crash about community permissions Fixes #11996
2023-08-28 19:56:03 +00:00
active: root.rootStore.chatCommunitySectionModule.isCommunity() && root.isPrivilegedUser
[#2813] Updating chat layout Switched to StatusAppThreePanelLayout as per new design for members list Closes #2813
2021-07-22 14:53:19 +00:00
desktop(community-settings): add overview and members settings this is first iteration for: #4938
2022-03-23 15:38:23 +00:00
sourceComponent: CommunitySettingsView {
fix(MembershipRequests): Remove MembershipRequestsPopup and set-up the navigation to CommunityMembersSettingsPanel Part of https://github.com/status-im/status-desktop/issues/9912
2023-04-06 11:11:57 +00:00
id: communitySettingsView
feat(@desktop): use emoji hash and identicon ring Closes: #4782
2022-03-09 10:27:32 +00:00
rootStore: root.rootStore
fix(shared-addresses): wrong account color and type - rename `watchOnlyAccounts` to `nonWatchAccounts` to reflect what the property returns - some warning fixes Fixes #12023
2023-08-29 15:28:41 +00:00
walletAccountsModel: WalletStore.RootStore.nonWatchAccounts
feat(TransferOwnershipPopup): Updated transfer ownership popup according to new design - Applied new design to transfer ownership popup. - Added support in storybook. - Added navigation to transfer ownership popup from community settings / owner token footer. - Added navigation to transfer ownership popup from community settings / overview. - Linked wallet send modal to the transactions popup with the needed pre-populated data. Closes #12171
2023-09-14 10:02:51 +00:00
sendModalPopup: root.sendModalPopup
chore(CommunityPermission): Use typed properties for CommunitiesStore Additionally, pass assets/collectibles models to HoldingsDropdown directly instead of store to reduce dependency.
2023-02-22 17:51:49 +00:00
feat(Community/FinaliseOwnership): Added finalise flow in the app - Button from community column. - Button from community overview. - Updated storybook pages (settings overview related) according to new components requirements. Part of #12174
2023-09-28 10:09:47 +00:00
finaliseOwnershipTransferPopup: finaliseOwnershipPopup
isPendingOwnershipRequest: root.isPendingOwnershipRequest
desktop(community-settings): add overview and members settings this is first iteration for: #4938
2022-03-23 15:38:23 +00:00
chatCommunitySectionModule: root.rootStore.chatCommunitySectionModule
fix(@desktop/sections): do not unload chat and communities sections during the switching between the sections
2023-03-17 18:58:07 +00:00
community: sectionItemModel
feat: disable community settings while in Testnet mode - display an info box when in wallet testnet mode with a CTA to disable it (functionality enabled for production builds only) - the CTA can be tested/seen via OverviewSettingsPanelPage storybook page Closes #11468
2023-07-24 11:31:31 +00:00
communitySettingsDisabled: root.communitySettingsDisabled
onCommunitySettingsDisabledChanged: if (communitySettingsDisabled) goTo(Constants.CommunitySettingsSections.Overview)
desktop(community-settings): add overview and members settings this is first iteration for: #4938
2022-03-23 15:38:23 +00:00
chore: consolidate & refactor popup handling - all remaining global popup components moved into a separate Popups entity - removed some static objects from the Global singleton (appMain, pinnedMessagesPopup, communityProfilePopup, sounds); rationale: singletons should not contain any state - fixed support for popups in storybook - fixed some warnings (most of them broke the popups in one way or the other)
2023-02-07 14:21:32 +00:00
onBackToCommunityClicked: root.currentIndex = 0
desktop(community-settings): add overview and members settings this is first iteration for: #4938
2022-03-23 15:38:23 +00:00
fix(MembershipRequests): Remove MembershipRequestsPopup and set-up the navigation to CommunityMembersSettingsPanel Part of https://github.com/status-im/status-desktop/issues/9912
2023-04-06 11:11:57 +00:00
Connections {
target: root.rootStore
function onGoToMembershipRequestsPage() {
root.currentIndex = 1 // go to settings
communitySettingsView.goTo(Constants.CommunitySettingsSections.Members, Constants.CommunityMembershipSubSections.MembershipRequests)
}
}
refactor(@desktop/chat-messages): `MessageContextMenuView` component updated
2021-12-14 14:19:55 +00:00
}
}
feat: channel permissions Closes: #10996, #10995, #10993, #10997, #9537
2023-06-08 11:01:01 +00:00
Component {
id: communityIntroDialogPopup
CommunityIntroDialog {
id: communityIntroDialog
property string communityId
feat: New design flows to integrate Revealing addresses... ... when joining Community functionality Closes #11138
2023-07-04 15:11:41 +00:00
loginType: root.rootStore.loginType
fix(shared-addresses): wrong account color and type - rename `watchOnlyAccounts` to `nonWatchAccounts` to reflect what the property returns - some warning fixes Fixes #12023
2023-08-29 15:28:41 +00:00
walletAccountsModel: WalletStore.RootStore.nonWatchAccounts
feat(shared-addresses): add loading state for checking permissions Fixes #11893
2023-08-22 18:04:58 +00:00
requirementsCheckPending: root.rootStore.requirementsCheckPending
feat(communities): Update permissions list for spectated community tokens model (#11803) Fixes: #11480 * hook up join popup to permission model * fix chats not being put in the permission model * make it work with channel permissions as well --------- Co-authored-by: Jonathan Rainville <rainville.jonathan@gmail.com>
2023-08-21 18:54:57 +00:00
permissionsModel: {
root.rootStore.prepareTokenModelForCommunity(communityIntroDialog.communityId)
return root.rootStore.permissionsModel
}
feat: New design flows to integrate Revealing addresses... ... when joining Community functionality Closes #11138
2023-07-04 15:11:41 +00:00
assetsModel: root.rootStore.assetsModel
collectiblesModel: root.rootStore.collectiblesModel
feat: channel permissions Closes: #10996, #10995, #10993, #10997, #9537
2023-06-08 11:01:01 +00:00
onJoined: {
feat(Communities): changes in import popup for public keys Also: refactor(communities), moved request to join funcs to communities module This is needed because we can now request to join from the Import popup Closes #11242
2023-07-21 17:21:11 +00:00
root.rootStore.requestToJoinCommunityWithAuthentication(communityIntroDialog.communityId, root.rootStore.userProfileInst.name, sharedAddresses, airdropAddress)
feat: channel permissions Closes: #10996, #10995, #10993, #10997, #9537
2023-06-08 11:01:01 +00:00
}
onCancelMembershipRequest: {
root.rootStore.cancelPendingRequest(communityIntroDialog.communityId)
mainViewLoader.item.isInvitationPending = root.rootStore.isCommunityRequestPending(communityIntroDialog.communityId)
}
feat(communities): Update permissions list for spectated community tokens model (#11803) Fixes: #11480 * hook up join popup to permission model * fix chats not being put in the permission model * make it work with channel permissions as well --------- Co-authored-by: Jonathan Rainville <rainville.jonathan@gmail.com>
2023-08-21 18:54:57 +00:00
onSharedAddressesUpdated: {
root.rootStore.updatePermissionsModel(communityIntroDialog.communityId, sharedAddresses)
}
feat: channel permissions Closes: #10996, #10995, #10993, #10997, #9537
2023-06-08 11:01:01 +00:00
onClosed: {
destroy()
}
}
}
feat(Community/FinaliseOwnership): Added finalise flow in the app - Button from community column. - Button from community overview. - Updated storybook pages (settings overview related) according to new components requirements. Part of #12174
2023-09-28 10:09:47 +00:00
// Components related to transfer community ownership flow:
Component {
id: finaliseOwnershipPopup
FinaliseOwnershipPopup {
id: finalisePopup
readonly property var communityData: root.sectionItemModel
readonly property var ownerToken: ModelUtils.getByKey(communityData.communityTokens,
"privilegesLevel",
Constants.TokenPrivilegesLevel.Owner)
communityName: communityData.name
communityLogo: communityData.image
communityColor: communityData.color
tokenSymbol: ownerToken.symbol
tokenChainName: ownerToken.chainName
accounts: WalletStore.RootStore.nonWatchAccounts
feeText: feeSubscriber.feeText
feeErrorText: feeSubscriber.feeErrorText
isFeeLoading: !feeSubscriber.feesResponse
onRejectClicked: Global.openPopup(declineOwnershipPopup)
onFinaliseOwnershipClicked: signPopup.open()
onVisitCommunityClicked: rootStore.setActiveCommunity(communityData.id)
onOpenControlNodeDocClicked: Global.openLink(link)
DeployFeesSubscriber {
id: feeSubscriber
readonly property TransactionFeesBroker feesBroker: TransactionFeesBroker {
communityTokensStore: root.rootStore.communityTokensStore
}
chainId: finalisePopup.ownerToken.chainId
tokenType: finalisePopup.ownerToken.type
isOwnerDeployment: true
accountAddress: finalisePopup.ownerToken.accountAddress
enabled: finalisePopup.visible || signPopup.visible
Component.onCompleted: feesBroker.registerDeployFeesSubscriber(feeSubscriber)
}
SignTransactionsPopup {
id: signPopup
title: qsTr("Sign transaction - update %1 smart contract").arg(finalisePopup.communityData.name)
totalFeeText: finalisePopup.isFeeLoading ? "" : finalisePopup.feeText
errorText: finalisePopup.feeErrorText
accountName: finalisePopup.ownerToken.accountName
model: QtObject {
readonly property string title: finalisePopup.feeLabel
readonly property string feeText: signPopup.totalFeeText
readonly property bool error: finalisePopup.feeErrorText !== ""
}
onSignTransactionClicked: {
root.rootStore.communityTokensStore.updateSmartContract(finalisePopup.communityData.id, finalisePopup.ownerToken)
close()
}
}
Connections {
target: root
onOwnershipDeclined: finalisePopup.close()
}
}
}
Component {
id: declineOwnershipPopup
FinaliseOwnershipDeclinePopup {
readonly property var communityData: root.sectionItemModel
communityName: communityData.name
onDeclineClicked: {
console.warn("TODO: Backend update notification center and display a toast: Ownership Declined!")
root.ownershipDeclined()
}
}
}
feat: info msg if owner is not awailable after community ownership change (#12560) feat: info msg if the owner is not available after community ownership change
2023-10-31 17:55:41 +00:00
Component {
id: controlNodeOfflineComponent
ControlNodeOfflineCommunityView {
id: controlNodeOfflineView
readonly property var communityData: sectionItemModel
readonly property string communityId: communityData.id
name: communityData.name
communityDesc: communityData.description
color: communityData.color
image: communityData.image
membersCount: communityData.members.count
communityItemsModel: root.rootStore.communityItemsModel
notificationCount: activityCenterStore.unreadNotificationsCount
hasUnseenNotifications: activityCenterStore.hasUnseenNotifications
onNotificationButtonClicked: Global.openActivityCenterPopup()
onAdHocChatButtonClicked: rootStore.openCloseCreateChatView()
}
}
feat(Community/FinaliseOwnership): Added finalise flow in the app - Button from community column. - Button from community overview. - Updated storybook pages (settings overview related) according to new components requirements. Part of #12174
2023-09-28 10:09:47 +00:00
// End of components related to transfer community ownership flow.
feat: channel permissions Closes: #10996, #10995, #10993, #10997, #9537
2023-06-08 11:01:01 +00:00
Connections {
target: root.rootStore
enabled: mainViewLoader.item
function onCommunityAccessRequested(communityId: string) {
if (communityId === mainViewLoader.item.communityId) {
mainViewLoader.item.isInvitationPending = root.rootStore.isCommunityRequestPending(communityId)
}
}
}
chore: split ChatLayout into a seprate file Preliminary work for the wallet. This way, AppLayout isn,t goign to be huge
2020-05-13 17:27:06 +00:00
}