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

205 lines
8.2 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"
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 "views/communities"
refactor(desktop/chat) Moving chat to new architecture Closes #3710
2021-10-01 15:58:36 +00:00
import "stores"
fix(@desktop/chat): intermittent with community invites Fixes: #6170
2022-06-21 11:44:20 +00:00
import "popups/community"
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
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(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
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
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
sourceComponent: chatItem.isCommunity() && chatItem.requiresTokenPermissionToJoin && !chatItem.amIMember ? joinCommunityViewComponent : chatViewComponent
}
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 ||
communityData.memberRole === Constants.memberRole.admin
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: 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
isInvitationPending: root.rootStore.isCommunityRequestPending(communityData.id)
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, {
communityId: communityData.id,
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: {
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
root.rootStore.cancelPendingRequest(communityData.id)
joinCommunityView.isInvitationPending = root.rootStore.isCommunityRequestPending(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
Connections {
target: root.rootStore.communitiesModuleInst
function onCommunityAccessRequested(communityId: string) {
if (communityId === joinCommunityView.communityData.id) {
joinCommunityView.isInvitationPending = root.rootStore.isCommunityRequestPending(communityData.id)
}
}
}
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
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 ||
root.sectionItemModel.memberRole === Constants.memberRole.admin
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
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
desktop(community-settings): add overview and members settings this is first iteration for: #4938
2022-03-23 15:38:23 +00:00
active: root.rootStore.chatCommunitySectionModule.isCommunity()
[#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
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(CommunityOverview): Add Community Overview banners Closes: #5978
2022-06-06 15:23:24 +00:00
hasAddedContacts: root.contactsStore.myContactsModel.count > 0
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
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
onJoined: {
root.rootStore.requestToJoinCommunityWithAuthentication(communityIntroDialog.communityId, root.rootStore.userProfileInst.name)
}
onCancelMembershipRequest: {
root.rootStore.cancelPendingRequest(communityIntroDialog.communityId)
mainViewLoader.item.isInvitationPending = root.rootStore.isCommunityRequestPending(communityIntroDialog.communityId)
}
onClosed: {
destroy()
}
}
}
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
}