Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Various suggestions (design/wording) #464

Open
ms-mialingvo opened this issue Jan 8, 2025 · 6 comments
Open

Various suggestions (design/wording) #464

ms-mialingvo opened this issue Jan 8, 2025 · 6 comments

Comments

@ms-mialingvo
Copy link
Collaborator

Follow-up from topic #452

  • Checking the mobile menu, I was confused by the hamburger-menu and the similar looking manage-grids-icon. On the desktop I have focused on the text only and haven't consciously noticed the hamburger menu. For the hamburger menu I was confused as it wasn't behaving the way hamburger menus usually do, namely with the menu appearing and disappearing vertically across all the screen width. I think a different icon for the "hide" click would make clearer what the action upon clicking is, maybe an "x" or a "<". And for the manage-grids-icon I was just confused because it looks pretty similar to a hamburger menu icon, I don't have a proper idea for an alternative, though.
  • For the 3 dots at the bottom for mobile view, I'd suggest to just hide the 'add online user' and 'add offline user' from the mobile view so there is enough space to list the 'i' icon for 'about' so that every menu item can be accessed directly. The option to quickly add users from the side menu is useful on the desktop but on mobile, (a) it won't be necessary often as main editing and creating doesn't take place in mobile and (b) it's already available under the user icon.
  • On that topic, the wording for creating users under 'change user' is not clearly written in my opinion. I'd change it to something like:
    "Add new account:
    Register an online user.
    Add an offline user."
  • Going through the setting tabs I'd also change some things in the language tab for clarity:
    "Grid content language" change to "Default grid content language", then add a sentence after the translation information, something like "The language selected here will be the default language upon opening the grid.", otherwise it's a bit confusing that it says 'you can have the grid in all languages but you have to select one language for the grid here'.
    "Preferred voice" change to "Default voice" and add some information here too. Something like "Voice for the default grid content language. To set the voices for multilingual gridsets, use the 'Change content language / voice' action."
@deinhofer
Copy link
Collaborator

Hi,
I totally agree with that:
"Going through the setting tabs I'd also change some things in the language tab for clarity:
"Grid content language" change to "Default grid content language", then add a sentence after the translation information, something like "The language selected here will be the default language upon opening the grid.", otherwise it's a bit confusing that it says 'you can have the grid in all languages but you have to select one language for the grid here'.
"Preferred voice" change to "Default voice" and add some information here too. Something like "Voice for the default grid content language. To set the voices for multilingual gridsets, use the 'Change content language / voice' action."

Currently it's confusing if you have a multilingual grid because you can also change the language with grid actions. Also when providing translations it should be noted to define a default language first, that is used as starting point for the other translations.

@ms-mialingvo
Copy link
Collaborator Author

ms-mialingvo commented Jan 24, 2025

@klues Could the last point (rewording in language tab) be done before the upcoming release, please? It would allow me to then update the manual with the correct paths/info for the new setup and to add the correct screenshots.

@klues
Copy link
Contributor

klues commented Jan 27, 2025

I've now already released the big release. But if it's important I can still rename the things in the language tab and release it afterwards.

"Default grid content language", then add a sentence after the translation information, something like "The language selected here will be the default language upon opening the grid.",

I would maybe rename it to Current grid content language and without any extra explanation. This would be clearest for me, because it's exactly what it is - it shows the current content language, which can be changed there in the settings and also via an element action that can be triggered by the user.

@ms-mialingvo
Copy link
Collaborator Author

I see. That name would be good too, though maybe Current language of the grid is a bit clearer. I'd nevertheless change
Grids can be translated to every language. To add or edit a translation use "Edit grid -> More -> Translate Grid".
to something like
Grids can be translated to every language. To add or edit a translation use "Edit grid -> More -> Translate Grid". Switch between languages with action elements.

And then Voice to Voice for current language with some info like
Set the voices for multilingual gridsets with action elements.

(Suggested link currently not working as currently only language is described in the manual, planning on updating that info today or latest tomorrow.)

@ms-mialingvo
Copy link
Collaborator Author

Suggested link currently not working as currently only language is described in the manual, planning on updating that info today or latest tomorrow.

Can you nevertheless adapt the text now so I can do the proper screenshots for the manual?

@ms-mialingvo
Copy link
Collaborator Author

Going through old comments I got reminded that we also had discussed and agreed on adding some info to 'prefered voice' to tell the user that that setting is not synchronised across devices.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants