On 07/17/2012 05:09 PM, Jirka Tomasek wrote:
Hi all,
so I went through UI Annoyances wikipage and divided the issues between
those that require design work to resolve and those that can be fixed
without design intervention.
The list of UI Annoyances is here:
https://www.aeolusproject.org/redmine/projects/aeolus/wiki/List_of_UI_Ann...
Most of the quickfixes are straightforward.The fixes which I think might
require some discussion are listed below. Feel free to comment on any of
the issues from the list or add the new ones you bump into.
* "Launch with errors" makes it sound like it will cause errors on purpose
- maybe rewording to something like: "Ignore errors during launch"
would do be enough?
* /pool_families uses both "Environments" and "Pool Families"
terminology (DISCUSS)
- I would prefer the Pool Families here to be keep it the same as
model name but I am not really sure on this one. Any recommendations?
* "Xml Deployable XML file doesn't resolve valid XML" is the worst error
ever
** it is {confusingly, awkwardly, poorly} worded and uses the word "XML"
three times in one sentence
** it doesn't actually indicate what's wrong with the XML -- we might as
well just say "Your XML is no good! Try again!"
- change the validation message to more reasonable one and include the
link to edit deployable xml?
I would like to start implementing the quick fixes by tomorrow.
Jirka
I added a few things to the wiki page:
Quick fixes:
- The order of the providers in the 'Choose a provider' dropdown is
changing after a provider has been enabled/disabled. The order should be
persistent
- There's no page where the user can overview which providers are
enabled and which are disabled. The new providers#index page could be
good place for it. Now it can only be checked on the show page of the
individual provider
- In case of validation error the form on provider_accounts#new seems to
properly persist the key and certificate field over the request. But
after fixing the error and submitting the form again, it complains about
the missing key and certificate
- The form of deployables#new and images#new have different default
value for editing the xml file
- On Launch time params page 'Cancel' is capitalized 'back' is not
- Inconsistent deployment pretty view cards on pools#index and
deployment#show. Why do we need 2 different kinds of deployment card?
Require design work:
- Forms do not reflect whether an attribute is optional or required
- Error reporting should be improved. In many cases we just return the
name of the exception to the user which is a bad UX. We should not
interact with the user via exceptions but process the exceptions and set
a custom message based on it.
Imre