Too many clicks to get to descriptions of fields (MGNLUI-2661)

[MGNLUI-2721] Show field descriptions and dialog help text everywhere Created: 28/Feb/14  Updated: 06/May/14  Resolved: 17/Apr/14

Status: Closed
Project: Magnolia UI
Component/s: forms
Affects Version/s: None
Fix Version/s: 5.2.4

Type: Sub-task Priority: Neutral
Reporter: Andreas Weder Assignee: Chunhua Liu
Resolution: Fixed Votes: 0
Labels: usability, ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLUI-2720 Show and hide all help texts at once,... Closed
relation
is related to MGNLUI-2811 Help texts are not displayed consiste... Closed
Template:
Date of First Response:

 Description   

Please research if we could always show all dialog help texts and all field descriptions in all dialogs, if a user clicks on the "?" in the header of any dialog.

The idea is to offer a convenient way to get to know a project setup by just "enabling help" once and get to see it everywhere.

Not all UI and technical issues may have been considered yet - please first research the implications and technical feasibility before investing full time in this feature.



 Comments   
Comment by Chunhua Liu [ 15/Apr/14 ]

Yes, We can display dialog help texts and field descriptions everywhere.
we can modify FormFieldWrapper.setHelpEnabled to automatically unfold or hide "help texts" and "descriptions of field".

FormFieldWrapper.java
    public void setHelpEnabled(boolean isHelpEnabled) {
        helpButton.setVisible(
                isHelpEnabled &&
                        helpDescription != null &&
                        !"".equals(helpDescription) &&
                        !errorAction.isVisible());
        if (!isHelpEnabled && helpSection != null) {
            hideHelp();
            return;
        }
        if (helpButton.isVisible() && helpSection == null) {
            showHelp();
        }
    }

but this issue maybe is repeat or similar to MGNLUI-2720.
so this issue can be fixed in MGNLUI-2720 together.

Comment by Daniel Lipp [ 15/Apr/14 ]

Pls resolve with "obsolete" so it's obvious we won't take any action on this ticket.

Comment by Andreas Weder [ 15/Apr/14 ]

Please note that the difference between MGNLUI-2720 and this issue is that this asks for the setting to become sticky across dialogs. While MGNLUI-2720 toggles all help texts in a single dialog, while this here remembers the setting across dialogs and thus will automatically show help texts in other dialogs, once shown using the button in the header in one dialog.

If that was clear, tant pis, if not, please re-open this issue and add the feature idea to the backlog.

Comment by Christoph Meier [ 15/Apr/14 ]

The above comment from Andreas i correct. The proposed change (FormFieldWrapper#setHelpEnabled) is part of a "simple solution"* for MGNLUI-2720, but it does not resolve this ticket here; it doesn't "open the help-text" sticky across dialogs.
So i reopen this ticket.

*) the simple solution oaslo doesn't properly resolve MGNLUI-2720; see description:
The latter should also hold if only some field descriptions have been "manually" opened: if I open description of field A and D, then click on "?" in the header, the description of field A and D is closed first. Another click on the "?" in the header then opens all descriptions again.
=> This cannot be ensured. For that, something more sophisticated is required.

Comment by Andreas Weder [ 15/Apr/14 ]

Ok. Just to be clear: this is not very important. It's an idea for a neat "help mode" feature which we thought would come for a cheap price, but nothing that has to be released as part of 5.2.4. It doesn't even have to go into maintenance. I don't mind if you convert this into an issue, mark it as "improvement" and take it out of this sprint.

Comment by Chunhua Liu [ 16/Apr/14 ]

By global variable setting to control "open the help-text" visible status for sticky across dialogs.

Comment by Christoph Meier [ 16/Apr/14 ]

It's sufficient if the "show descriptions"-feature is sticky only during a session. (I just asked Andreas.)
Having said this, just use a static variable on the GWT-widget, so we can avoid using storage or cookies.

(If it should be "super-sticky" we'd probably would store the state on the server on the profile ...)

Comment by Chunhua Liu [ 17/Apr/14 ]

According to static variable of DialogHeaderWidget to control help icon display across dialogs, because that DialogHeaderWidget is a GWT class, it run in browser, so that static variable's scope is current page, it mean that if we refresh current page or open a new page, its value will be reset.

Generated at Mon Feb 12 08:59:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.