Closed grctest closed 1 year ago
Further optimization is required if the user plans a multi thousand operation based prompt. If there are thousands of assets and account names to fetch, then we face making 50-100 batched queries to the network which will get rate limited and eventually blocked.
We could either introduce a delay between queries, to avoid rate limit issues, or we could switch to a simpler prompt response which doesn't involve network queries at the expense of prompt readability.
Ideally, as the user clicked through the paginated prompt contents, batches of content would be requested from the network, however the current structure of the prompt popups is that they launch once they have all operation parameters processed.
Related blog post: https://hive.blog/hive-120117/@nftea.gallery/new-custom-airdrop-functionality-introduced-to-the-bitshares-airdrop-tool-in-v0-2-9-check-it-out
Switched from requesting get_full_accounts to get_objects, optimizing prompts with large quantities of objects.
Change made in #257 in the following commit: https://github.com/bitshares/beet/pull/257/commits/fad8c26d01e9d3bef06aec24923b3c6117582176
PR now merged into the develop branch, users can now paginate through multiple operations in a single transaction prompt.
Is your feature request related to a problem? Please describe.
Having recently created prompts with 50+ operations in them with the airdrop tool, I've observed some issues with the prompt UX for multiple operations.
Namely:
Describe the solution you'd like
Perhaps, instead of a scroll area of text separated by new lines "\n", each operation could have its own card, perhaps still scrollable, or one at a time with the option to switch between them.
Provide high level summary of many operations as an intro description, e.g. list each operation type used, list the total quantity of BTS being transfered/sold, provide a total fee estimate.
Describe alternatives you've considered
Provide summary description lines of text prior to the operation lines of text.
Additional context
Not massively bothered by this, just wondering if anyone has a preferred prompt UX to implement?
Perhaps increasing the size of prompt windows would also help make the lines of text readable, a further small UX tweak.