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 diplicity orders detail & layout to web client #44

Open
bsweezy opened this issue Jul 30, 2017 · 2 comments
Open

Add diplicity orders detail & layout to web client #44

bsweezy opened this issue Jul 30, 2017 · 2 comments

Comments

@bsweezy
Copy link

bsweezy commented Jul 30, 2017

Access the detailed and dense list of order resolutions to the web client that you can find in diplicity (see attached comparison). The diplicity version provides more detail about why orders to do not succeed ("ErrBounce:den"). The diplicity version also allows you to see MANY more orders on one screen because it is denser--requiring MUCH less scrolling. Because on the web client this order list scroll bar is already inside a web page which may have its own scroll bar, scrolling is particularly challenging.

image

===========
A group of 7 of us did a live game yesterday around a physical board game map, where we used iphones, ipads, and android devices to play the same game--this is one of a series of issues we opened related to our experience. It was a great overall experience! I'm so impressed at this project's progress.

@spamguy
Copy link
Owner

spamguy commented Jul 30, 2017

Thanks for the positive thoughts! I have many hopes for this project, and stuff like this keeps me going.

In general I would rather stick with my current approach. Diplicity's comes across more as a raw log dump, whereas I'm seeking a human friendly interpretation. That said, there is room for improvement.

  • Squish orders a little tighter together. The current margins are Material Design compliant, but understandably tedious for scrolling.
  • Acknowledge successful orders as such, perhaps through a checkmark or something green.
  • You obviously noted the use of hovers to discover reasons for failure. This has a couple gaps:
    • Mobile users can't use them. Oops.
    • The UI doesn't make it clear these hovers exist.

@bsweezy
Copy link
Author

bsweezy commented Jul 31, 2017

Thanks!

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

No branches or pull requests

2 participants