borisstoyanov opened a new issue #4798:
URL: https://github.com/apache/cloudstack/issues/4798
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and master branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Improvement Request
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
UI
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on master
branch.
-->
~~~
4.16
~~~
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
Should be browser/OS agnostic
##### SUMMARY
<!-- Explain the problem/feature briefly -->
This could be interesting to any UI/UX engineer, not required huge domain
knowledge which usually turns down candidates.
Surely our new UI is great, but there’s some things that could be improved
like for example:
Being able to navigate without mouse and use shortkey – for example when on
the dashboard when the user presses T, he could be directly transitioned to
Templates. Or I for infrastructure, G – global settings, H for hosts etc..
While in networks/instances/volumes press A – add item(network,volume etc).
Same goes for all buttons inside a page like Instances (stop, start, destroy
etc)
Confirm dialogues with key – This is not working consistently, some dialogue
windows have it some do not. But surely it’ll be great if we can confirm by
pressing Enter or Space and cancel by Esc.
Forms submission improvements – For example, when deploying instance if you
simply click ok without selected network it will prompt you with error and then
you’ll need to scroll back to the network place and add it. We could be more
intuitive and automatically move the focus of the user back at the networks
place in the form, where user can easily add or select a network.
Placement of buttons and forms – I’ve pointed this as debatable since it’s
more of a UX discussion, which may end up with a decision ‘there is nothing to
fix’. The idea is to think about questions as is this form intuitive enough, or
is this button placed good, maybe there’s a more suitable place for it. Etc.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
