RFC UI annoyances - "quick fixes" and "require design work"

Jirka Tomasek jtomasek at redhat.com
Tue Jul 17 15:09:05 UTC 2012


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_Annoyances

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fedorahosted.org/pipermail/aeolus-devel/attachments/20120717/fd3a1553/attachment.html>


More information about the aeolus-devel mailing list