Skip to content
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

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

jarolrod
Copy link
Member

@jarolrod jarolrod commented Feb 28, 2024

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:

  • Ban buttons
  • Hover hints
  • Disconnected state instead of flying back to the peers table
  • Smart text fixups
Screenshot 2024-02-28 at 3 53 43 AM

Link to github actions build artifacts.

Build Artifacts

Copy link
Contributor

@johnny9 johnny9 left a 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Contributor

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
Copy link
Contributor

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
Copy link
Contributor

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

QML is camelCase

Copy link
Contributor

@MarnixCroes MarnixCroes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good.

onion address can be a bit cut off when not on full window
image

nit, the spacing of Ping wait looks a bit odd
image

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; }}
Copy link
Contributor

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

Copy link
Contributor

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.

Copy link
Contributor

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.)

Copy link
Contributor

@D33r-Gee D33r-Gee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On Ubuntu 22.04 and Android arm7 (Galaxy A13 5G)
tACK 4909ba5 c33abef 6480cfe

Copy link
Contributor

@pablomartin4btc pablomartin4btc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tACK 4909ba5

Screenshot from 2024-03-13 12-53-22

@jarolrod jarolrod marked this pull request as draft March 20, 2024 08:01
@jarolrod
Copy link
Member Author

draft until I fix the line spacing when text wraps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants