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

Epic: Show users that a resource is pre-release #7378

Open
birchamp opened this issue Aug 1, 2022 · 7 comments
Open

Epic: Show users that a resource is pre-release #7378

birchamp opened this issue Aug 1, 2022 · 7 comments

Comments

@birchamp
Copy link
Contributor

birchamp commented Aug 1, 2022

Issue:

Currently, once a user chooses to see pre-releases in the update dialog, those resources appear like any other resources, both in the update dialog and in the GL dropdown. Users need some indicator that they are working with a pre-release. This could be as simple as changing the color of the text or an asterisk next to the name.

DoD:

There is something consistently different about how the name of a GL resource appears to indicate to the user that it is a pre-release. This should be true wherever the name of the resource appears.

Details:

Updates Dialog
Gl Dropdown
Scripture pane add resources
Scripture pane title (hover text)
Expanded Scripture pane (hover text)

@birchamp
Copy link
Contributor Author

birchamp commented Aug 4, 2022

example: [English - Door43] - Pre-release

@PhotoNomad0 PhotoNomad0 self-assigned this Aug 10, 2022
@PhotoNomad0
Copy link
Contributor

PhotoNomad0 commented Aug 10, 2022

Notes - proposed logic for flagging pre-releases in the GL dropdown list:

It's always more complicated than we would like:

Flagging based on the tool dependencies:

  • in WA - the default GL alignment bible is pre-release or the original language bible is pre-release
  • in tW - the default original language bible is pre-release or the tWL is pre-release
  • in tN - the default GL alignment bible is pre-release or the tN is pre-release

The default GL aligned bible for a language and owner is based on searching starting with ult, glt and then the others until we find a bible that is aligned for that book.

@birchamp @elsylambert

@birchamp
Copy link
Contributor Author

So where would this affect what the users see?

@PhotoNomad0
Copy link
Contributor

PhotoNomad0 commented Aug 11, 2022

So where would this affect what the users see?

The GL dropdown list for each tool. They are all different.

@PhotoNomad0
Copy link
Contributor

@birchamp @elsylambert - it gets complicated determining the resource dependencies for each GL resource option. Maybe for pre-release GL dependencies we could show which resources are pre-release, such as for tN tool the extreme case would be:

[English (en) - test_org] - Pre-release - tN, tA, en_ult, ugnt

for tW:

[English (en) - test_org] - Pre-release - tW, tWL, en_ult, ugnt

for WA

[English (en) - test_org] - Pre-release - en_ult, ugnt

@PhotoNomad0
Copy link
Contributor

Split into two issues

@PhotoNomad0
Copy link
Contributor

@birchamp @elsylambert ^^^

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

No branches or pull requests

2 participants