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

UI: Navigating the complex data inside of a transaction receipt #470

Open
gabriel-indik opened this issue Dec 6, 2024 · 4 comments
Open
Assignees
Labels
enhancement New feature or request stale

Comments

@gabriel-indik
Copy link
Contributor

What would you like to be added?

The experience for "picking" a sub-transaction in an Atomic (4) one needs to give you some insight into which are which without picking one
Is the whole State Receipt available yes/no?
The Domain

Why is this needed?

Make the UX easier to navigate through and more effective.

@gabriel-indik gabriel-indik added the enhancement New feature or request label Dec 6, 2024
@gabriel-indik
Copy link
Contributor Author

Proposal: replace the dropdown control in the upper section of the transaction details dialog box with a table where each entry has a radio control and represents a transaction, indicating its id (in short format), domain and whether it has a receipt or not. Mockup:

image

@peterbroadhurst do you think the design above would provide a good UX?

@peterbroadhurst
Copy link
Contributor

Regarding the yes/no - on Receipt let me give some examples of the actual complexity we're trying to navigate as humans when we're clicking this list:

  1. The transaction was submitted by me, I have:
    • A transaction object
    • A receipt object
    • A state receipt
    • A domain receipt
    • The domain is pente
  2. The transaction was submitted by me, and I only have:
    • A transaction object
    • Debug information about what's happening with the transaction
    • ... because the transaction is still going through
  3. The transaction was submitted by someone else, but I am included fully so I have:
    • A receipt object
    • A state receipt
    • A domain receipt
    • The domain is pente
  4. The transaction was submitted by someone else, and I'm not included so I have:
    • A state receipt that is incomplete

This certainly isn't a complete list of possibilities, but it hopefully illustrates the enum style situation we're in here, and why I'm not sure it's a yes/no on one english word (particularly "receipt" which is very loaded).

@gabriel-indik
Copy link
Contributor Author

Adding the exact same information above, but in table format to see if it might make it easier to collaborate on a design for that portion of the UX:

image

@gabriel-indik gabriel-indik self-assigned this Dec 9, 2024
Copy link

github-actions bot commented Jan 6, 2025

This issue is stale because it has been open 30 days with no activity.

@github-actions github-actions bot added the stale label Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale
Projects
None yet
Development

No branches or pull requests

2 participants