BizDani
Member
In the trader, to improve efficiency of space and time (starting to sound like a physics problem now), how about rolling-up identical trades with quantity columns on the post, view, accept, and delete processes. Most beneficial on post and delete where a confirmation dialog is presented with each submission and in the view where lots of paging and space is taken for identical items.
So when posting a trade you can enter how many of the trade you would like to post (could be a standard numeric entry field that can be manually entered or arrow-ed up and down or whatever fabulous UI controls the devs have at their disposal or can imagine these days)
Same on the accept side - enter or arrow up/down how many you want and click accept.
The capability to accept or post should be limited to what you are capable of accomplishing based on inventory etc.
Common values on offer, demand and trader would create a unique row. The counts would move up and down for the given row as trades are posted or accepted.
Saves space, saves paging, saves clicks. Of course if the relational architecture in the db (if they use a relation db) is such that this is not easily amended with a joining table for quantities or something it may be either resource intensive on the system to conduct the rollup's or intensive on the developers to convert the architecture and transform existing data.
Anyway - seems a useful UI/UX improvement if reasonably accomplished.
Thanks and have a great day!
BizDani
So when posting a trade you can enter how many of the trade you would like to post (could be a standard numeric entry field that can be manually entered or arrow-ed up and down or whatever fabulous UI controls the devs have at their disposal or can imagine these days)
Same on the accept side - enter or arrow up/down how many you want and click accept.
The capability to accept or post should be limited to what you are capable of accomplishing based on inventory etc.
Common values on offer, demand and trader would create a unique row. The counts would move up and down for the given row as trades are posted or accepted.
Saves space, saves paging, saves clicks. Of course if the relational architecture in the db (if they use a relation db) is such that this is not easily amended with a joining table for quantities or something it may be either resource intensive on the system to conduct the rollup's or intensive on the developers to convert the architecture and transform existing data.
Anyway - seems a useful UI/UX improvement if reasonably accomplished.
Thanks and have a great day!
BizDani
Last edited: