-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat/building simple send #16868
base: master
Are you sure you want to change the base?
Feat/building simple send #16868
Conversation
da50bdc
to
d350cfb
Compare
Jenkins BuildsClick to see older builds (57)
|
59b4155
to
9f2a213
Compare
c52e770
to
89daa99
Compare
9f2a213
to
51fc469
Compare
2a789a7
to
93224cb
Compare
93224cb
to
153f94b
Compare
…dialog resizing for simple send fixes #16836
…ed when Simple send is scrolling
…ched outside of storybook
56dffde
to
017cf6c
Compare
Screen.Recording.2024-12-10.at.9.24.52.AM.movI think it now works the way you mentioned @benjthayer ;)
Fixed, I bring in the sticky header after a bit of padding.
I cant see it in design, but I tried some playing with FastBlur and it looks like this Screen.Recording.2024-12-09.at.10.45.24.PM.mov
Fixed in this task #16834 |
…simple send fixes #16918
98aeb7e
to
16e67a2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work! 👍
|
||
loading: loadingCheckbox.checked | ||
|
||
onReviewSendClicked: console.log("review send clicked") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpick: The Logs
and LogsAndControlsPanel
components are not really used. Did you mean to log this in the LogsAndControlsPanel
? Otherwise just a simple panel would do. Same on all pages
@@ -32,7 +33,8 @@ Dialog { | |||
anchors.centerIn: Overlay.overlay | |||
|
|||
padding: 16 | |||
margins: 64 | |||
// by design | |||
margins: root.contentItem.Window.window.height <= 780 ? 28: 64 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need an extensive regression on all modals? Should be harmless, but you never know :D
|
||
import AppLayouts.Wallet.views 1.0 | ||
|
||
Rectangle { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be nice to inherit a Control
instead. Gives more freedom for styling or adapting this to different views.
/** Output signal to request signing of the transaction **/ | ||
signal reviewSendClicked() | ||
/** Output signal to request fetching fees **/ | ||
signal fetchFees() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd keep the SendModal
as simple as possible and UI only. Meaning that it doesn't have additional logic like detecting when new fees are required.
If we detect this here, the fees responsibility will be split between two components:
- Send modal to detect when a new fee is required based on what the user changes in the UI
- Other component to aggregate the user input from the
SendModal
and request the fees onfetchFees
signal.
Another way would be for the SendModal to become a simple form. Any change in the form can be handled by the user of the SendModal
. As a result, the logic of updating the fees is transparently handled in a single place, outside of the SendModal
.
WDYT?
**/ | ||
required property var flatNetworksModel | ||
/** true if testnet mode is on **/ | ||
required property var areTestNetworksEnabled |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
required property var areTestNetworksEnabled | |
required property bool areTestNetworksEnabled |
required property var areTestNetworksEnabled | ||
/** whether community tokens are shown in send modal | ||
based on a global setting **/ | ||
required property var showCommunityAssetsInSend |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
required property var showCommunityAssetsInSend | |
required property bool showCommunityAssetsInSend |
fixes #16836
What does the PR do
This PR add some dummy components + some actual ones in order to fix a mechanism for the dialog sizing.
Please not even though the AccountSelector, TokenSelector and NetworkFilter are added in this PR they are not worked on completely yet and is still something that is WIP under Epic #16696
Please note this PR doesn't cover QML Units tests, I will work on them next.
The Recipient selector is only temporary one and not done yet TBD under #16916
Affected areas
SimpleSend.qml
Architecture compliance
My PR is consistent with this document: Status Desktop Architecture Guide
Screenshot of functionality (including design for comparison)
Screen.Recording.2024-12-04.at.7.14.49.PM.mov
Screen.Recording.2024-12-04.at.7.19.35.PM.mov
Screen.Recording.2024-12-08.at.11.21.18.PM.mov