[Horizon] Enhance forms usability and helping system in Horizon / OpenStack UI
TBD
Blueprint information
- Status:
- Complete
- Approver:
- Jaromir Coufal
- Priority:
- Low
- Drafter:
- Jaromir Coufal
- Direction:
- Approved
- Assignee:
- Jaromir Coufal
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Slow progress
- Milestone target:
-
juno
- Started by
- Jaromir Coufal
- Completed by
- Pieter
Related branches
Related bugs
Sprints
Whiteboard
Addressed by following wireframes: http://
Implementation pushed to Juno - waiting for Juno master to be opened.
[lblanchard 05-27-2014] Jarda - Do you think that this BP should contain some of the work I've done around improving the inline help messages in Horizon? Here is a link to the wiki page I created around the proposal...
https:/
Ultimately, I think we need to add inline help to a fair amount of fields where it is currently missing and also have a solution that works for form elements other than input boxes.
[2014-05-29 jcoufal] Hi Liz, this proposal is about covering general approach of how the hints / inline help / global help should work together and what to prepare with implementation. I didn't get into concrete situations, so if you can help in listing down what are the exact fields which need a help text and what text should be displayed there, it would be awesome!
[raghuram-gundimeda 06-30-2014] Hi Jarda, Greetings! Thanks to Liz, I am now working on a design for the UX blueprint "Suggest Ways to Add Contextual Help to Horizon" (https:/
One goal of this effort is to also arrive at a common interaction solution to provide contextual / inline help for any / all types of input elements (input box, drop list, check box, etc.).
A couple of points about my design proposal are:
• No static display of inline help text
• Inline help text displays as the user ‘moves’ to focus on a input widget - using either mouse or Tab key navigation, and is visible as long as he works with that widget. No deliberate mouse-over effort required here
• This interaction behavior is common for any input widget
I will share the proposal with you soon, but just thought I'll check with you to see if we have an overlap here on our efforts.
BTW, the link to your wireframes pdf seems to be broken. Thanks!
