[
https://issues.apache.org/jira/browse/IGNITE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791571#comment-14791571
]
Dmitriy Setrakyan commented on IGNITE-843:
------------------------------------------
I had another look at UI and have the following comments that apply to all
screens in general. I am using a numbered list, so that we can keep track which
change was fixed by its number.
# What’s Now -> On This Screen
# What’s next -> Next Steps
# Use normal popup dialog when leaving screen with unsaved changes (do not use
standard web browser popup). The popup should have an option to Save before
leaving the screen.
# "New" button on all the screen should be renamed to describe the action: "Add
cluster", "Add Cache", etc.
# For multi-select dropdown, whenever names are short, we should list the names
instead of the number of entries selected. This does not work for metadata
selection, as class-names are too long, so let's keep the number there.
# Cache (add) should take a user to the New Cache screen (no need to force the
user to explicitly press "New" again on the cache screen. Same goes for other
screens with similar behavior.
# Red tooltips look to offensive. Can we try changing the background of
tooltips to blue?
# Instead of having a hidden "copy" action inside the button, let's add
explicit button called "Clone"
# We should not show the security token on UI screen (should be
"**************" with "Show Token" link next to it). Would also be nice to add
"Copy to clipboard" icon next to it as well.
# Every time we show the security token, we should provide a tooltip explaining
what it is for.
# Not sure why "Reset password" screen shows the security token. I would prefer
that it shows the email address.
# After the password was reset, user should have a message on the screen: Your
password has been reset, please [link: login].
# Assigning metadata to caches one-by-one is inconvenient. User should be able
to associate multiple or all metadata with a cache in one action.
# User should have a confirmation popup if he decides to change the security
token.
# Load from Database wizard should provide instructions on how to change the
database driver.
# XML code snippet does not have data source. I think we should provide a
sample data source (user should clearly see that it is a sample).
> Web configuration tools development
> -----------------------------------
>
> Key: IGNITE-843
> URL: https://issues.apache.org/jira/browse/IGNITE-843
> Project: Ignite
> Issue Type: Task
> Components: wizards
> Affects Versions: sprint-5
> Environment: Specific frameworks:
> # Main SPA stack: HTML5 / LESS / AngularJS 1.3.x / Bootstrap 3.x
> # Auxiliary: jQuery 2.x / AngularJS UI 0.x
> # HTTP server: node.js
> # Tools: Grunt, Lodash 2.x, Font-Awesome 4.x, Animate.css, ngTable
> Install node.js locally.
> Install Angular, LESS, and Grunt plugins into IDEA.
> Use LESS instead of CSS.
> Reporter: Alexey Goncharuk
> Assignee: Alexey Kuznetsov
> Fix For: ignite-1.5
>
> Attachments: ig-843.png
>
>
> Frameworks to be used:
> # Bootstrap
> # AngularJS
> # NodeJS
> # MongoDB
> Web control Center will communicate with Ignite Cluster via special
> lightweight proxy (so called web-agent) implemented on web-sockets.
> Test server: http://104.197.2.239
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
