Skip to content

OH2-444 | Add help support to text field component#711

Open
SteveGT96 wants to merge 3 commits intoinformatici:developfrom
SteveGT96:feature/OH2-444-field-tooltips-hints-helps
Open

OH2-444 | Add help support to text field component#711
SteveGT96 wants to merge 3 commits intoinformatici:developfrom
SteveGT96:feature/OH2-444-field-tooltips-hints-helps

Conversation

@SteveGT96
Copy link
Contributor

@SteveGT96 SteveGT96 commented Jan 6, 2025

See OH2-444

@SteveGT96
Copy link
Contributor Author

Hello @mwithi !

Here I've just the component with a demo usage. In orther to complete, I'll need to know all places places you want to show help/hint, and help/hint messages.

@SteveGT96
Copy link
Contributor Author

@SilverD3 , could you review code ?

@mwithi mwithi requested a review from SilverD3 January 9, 2025 00:15
@mwithi
Copy link
Member

mwithi commented Jan 9, 2025

Here I've just the component with a demo usage. In orther to complete, I'll need to know all places places you want to show help/hint, and help/hint messages.

Hi @SteveGT96, easy answer: I think it should be there for every field, checkbox, combo, etc... It would explode the number of translations and maybe the UI will be burdened, but it could also improve the user experience a lot.

Could you ask advice to the designers too?

@SilverD3
Copy link
Contributor

SilverD3 commented Jan 9, 2025

Here I've just the component with a demo usage. In orther to complete, I'll need to know all places places you want to show help/hint, and help/hint messages.

Hi @SteveGT96, easy answer: I think it should be there for every field, checkbox, combo, etc... It would explode the number of translations and maybe the UI will be burdened, but it could also improve the user experience a lot.

Could you ask advice to the designers too?

We don't need to add "hint" on all form fields as must of them as self-explanatory. Instead, we could identify the ones that aren't explicit and add hint these fields

@SteveGT96
Copy link
Contributor Author

Here I've just the component with a demo usage. In orther to complete, I'll need to know all places places you want to show help/hint, and help/hint messages.

Hi @SteveGT96, easy answer: I think it should be there for every field, checkbox, combo, etc... It would explode the number of translations and maybe the UI will be burdened, but it could also improve the user experience a lot.

Could you ask advice to the designers too?

As @SilverD3 just said above, must of the fields are self-explanatory. You could just give us the list of specific fields that you think they need more attention from the user and also provide related hints to show.

WDYT ?

@mwithi
Copy link
Member

mwithi commented Jan 9, 2025

As @SilverD3 just said above, must of the fields are self-explanatory. You could just give us the list of specific fields that you think they need more attention from the user and also provide related hints to show.

WDYT ?

Well, easy answer also here: if you already know what fields are self-explanatory just leave them alone. It is easier than making now a list of all other fields with related translations... just make a proposal for a whole module (e.g. ward) so we can also see the expected result, because my concern is more about the design...
Is the "help" add as part of the base component? If so, it is automatically added whenever that component is used...

@mwithi
Copy link
Member

mwithi commented Mar 12, 2026

@SteveGT96 if this work is still valid, please align after #747

@mwithi mwithi added the question Further information is requested label Mar 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

question Further information is requested

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants