-
Notifications
You must be signed in to change notification settings - Fork 22
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
Create a Dune Analytics list for orders #312
Comments
I really like the idea of a bid table. |
I marked the feature with high prio, but we should only implement it in the froont-end, once we have dune dashboards |
actually will create new issue for that |
I don't like it in the same page, too crowded, would strongly prefer to have it as a toggle. @gabitoesmiapodo What do you think? |
I'm inclined to think that it will be too crowded, yeah. But it will depend on how many columns there are in the table, among other things. It may look OK with 4 columns, but if we add more later (and that's what usually happens...) we will run into trouble. The form could be narrower, though, we don't need it to be too wide. Anyways: what's the most important data the users need to have available all the time to take decisions? Do they need to compare data from the chart and the table? Do they need to compare this data against the data at the top of the section (Auction Details)? If that's the case, that's what should be available for the users all the time, and maybe we need to put the form on a toggle, or to use a different layout. We could even do something like: 1st row: Auction Details (we will probably add more info in #152) |
Done at the moment. Alex will create a ticket with next to do. |
Create a Dune Analytics list that shows all orders
The first iteration should have the following columns:
| Price | Amount | Sum | My Size %
Amount
that the bid of the user hasPossible button location
Marked with the red rectangle:
References to orderbook lists
A few images for inspiration.
Binance:
dYdX:
@cmagan Let me know if you think this would be enough.
The text was updated successfully, but these errors were encountered: