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
Add PeerDetails page [Alternative] #388
base: main
Are you sure you want to change the base?
Conversation
b7161c5
to
4909ba5
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.
Looks really good. Only thing that stood out to me was the arrow icon was slight too small but that difference makes it harder to see.
value: Row { | ||
IconButton { | ||
iconLocation: details.direction === "Inbound" ? "image://images/arrow-down" : "image://images/arrow-up" | ||
icon.height: 9 |
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.
icon.height: 9 | |
icon.height: 11 |
Add 2 pixels to compensate for the ~20% padding around the icon source. Makes it closer to the figma and also easier to see.
|
||
spacing: 10 | ||
Pane { | ||
id: key_field |
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.
QML is always camelCase
} | ||
} | ||
Component { | ||
id: peer_details |
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.
QML is camelCase
ValText { text: permissionsRow.permissionsValue; } | ||
} | ||
Component { | ||
id: not_permissioned |
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.
QML is camelCase
KeyValueRow { key: KeyText { text: qsTr("User agent"); } value: ValText { text: details.userAgent; }} | ||
KeyValueRow { key: KeyText { text: qsTr("Services"); } value: ValText { text: details.services; }} | ||
KeyValueRow { | ||
id: transaction_relay_row |
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.
QML is camelCase
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.
bottomPadding: 5 | ||
|
||
KeyValueRow { key: KeyText { text: qsTr("Address"); } value: ValText { text: details.address; color: Theme.color.neutral9; }} | ||
KeyValueRow { key: KeyText { text: qsTr("VIA"); } value: ValText { text: details.addressLocal; color: Theme.color.neutral9; }} |
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.
maybe VIA could be displayed only when it has a value?
for example, for an onion peer there is no VIA
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 do agree, unless there's reason for leaving it empty.
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.
As I saw in previous approach of the PeerDetails
page #387, perhaps a "N/A
" could be displayed or "-
"(as it's shown in the description above)? (e.g.)
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.
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.
tACK 4909ba5
draft until I fix the line spacing when text wraps |
Alternative to #387 which expands to think about a reusable row component, allowing to load any element(s) to the value field, not hardcoding in a height of 21 for a row (but still ensuring it's a minimum of 21), proper icon usage for N/A cases, dummy net indicators in place
TODO:
Link to github actions build artifacts.