Skip to content

display warning for latest IDE versions on the loading screen #8028

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

Closed
akosyakov opened this issue Feb 4, 2022 · 11 comments · Fixed by #8783
Closed

display warning for latest IDE versions on the loading screen #8028

akosyakov opened this issue Feb 4, 2022 · 11 comments · Fixed by #8783

Comments

@akosyakov
Copy link
Member

akosyakov commented Feb 4, 2022

For latest versions like VS Code Insiders and EAP of JB products we should display a warning at all phases of the loading screen and provide an action to switch to restart a workspace with a corresponding stable version of a selected product.

Designs

Preparing Running
Preparing Running

See design specs.

@akosyakov
Copy link
Member Author

@gtsiolis we will need a design for it.

cc @loujaybee

@loujaybee
Copy link
Member

In addition to this, I think we need to review our documentation and copy-text to ensure that the expectations are set with users properly. If we have this flag on the workspace loading, I think copy text such as "what does this mean" which links to docs about the insiders and explains how it works / user expectations would also be useful.

@loujaybee
Copy link
Member

loujaybee commented Mar 2, 2022

@gtsiolis we will need a design for it.

@akosyakov - It would be nice if designed, but I wouldn't necessarily wait a design on this one as we could do something simple, draft an approach / PR and tweak based on feedback from @gtsiolis et al. We can also implement this incrementally, there are various places we can show this information, just starting with the workspace loading screens etc would help

@akosyakov
Copy link
Member Author

Agree, to be clear it should be the same for EAP of JB products in sense of docs.

@loujaybee
Copy link
Member

loujaybee commented Mar 2, 2022

Also, this relates to: #7026.

In future I think we should consider having less stable features more clearly documented, e.g. Chrome Canary is a separate product / download so it's very clear. Or with the JetBrains EAP version's/products marked very clearly as EAP.

@loujaybee
Copy link
Member

Created a companion issue in website docs: https://github.com/gitpod-io/website/issues/1700

@akosyakov akosyakov moved this to Scheduled in 🚀 IDE Team Mar 2, 2022
@akosyakov
Copy link
Member Author

It would be nice if designed, but I wouldn't necessarily wait a design on this one as we could do something simple, draft an approach / PR and tweak based on feedback from @gtsiolis et al.

put in scheduled for IDE team as well

@jeanp413
Copy link
Member

jeanp413 commented Mar 7, 2022

@mustard-mh you could work on this too

For latest versions like VS Code Insiders and EAP of JB products we should display a warning at all phases of the loading screen and provide an action to switch to restart a workspace with a corresponding stable version of a selected product.

@mustard-mh mustard-mh self-assigned this Mar 9, 2022
@jeanp413 jeanp413 moved this from Scheduled to In Progress in 🚀 IDE Team Mar 16, 2022
@gtsiolis
Copy link
Contributor

fyi: I've added the specs in the issue description.

@filiptronicek
Copy link
Member

@gtsiolis do you think it would make sense to make this user-dismissible or rather to stuff it in every user's face all the time to make sure?

What about maybe a way for the user to minimize it to just a ⚠️ icon somewhere that would stay there forever, making (upon focus / click) a pop up / tooltip with this exact message possible?

@gtsiolis
Copy link
Contributor

gtsiolis commented Mar 17, 2022

do you think it would make sense to make this user-dismissible or rather to stuff it in every user's face all the time to make sure?

I swayed between making this dismissible. Here're some thoughts on this:

  1. It makes sense to not make it dismissible as the goal of this is to make users aware of a user preference that could be breaking the user experience.
  2. Making this dismissible once could create an unessasary habbit of users wasting time on dismissing a modal that only exists for a few seconds until the workspace is up and running.
  3. Making it dismissible forerever will cancel the goal of this to make users aware of the preference.
  4. Last but not least, long term we could allow users to hold and change editor while the workspace is loading.

What about maybe a way for the user to minimize it to just ...

This could be interesting and useful long term. Also, currently thinking of making this more compact as @mustard-mh is working on this in #8783 since it can grab quite a lot of vertical space. For example, we could introduce a simpler or less verbose alert component variation without s background, etc. But we can certainly improve this in the next iteration.

BEFORE AFTER (WIP)
Screenshot 2022-03-17 at 11 31 49 PM (2) Screenshot 2022-03-17 at 11 33 40 PM (2)

Thanks for the feedback, @filiptronicek! 🙏

@mustard-mh mustard-mh moved this from In Progress to In Review in 🚀 IDE Team Apr 7, 2022
Repository owner moved this from Needs Design to Done in 🍎 WebApp Team Apr 11, 2022
@felladrin felladrin moved this from In Review to Awaiting Deployment in 🚀 IDE Team Apr 11, 2022
@felladrin felladrin moved this from Awaiting Deployment to Done in 🚀 IDE Team Apr 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Status: Done
Development

Successfully merging a pull request may close this issue.

7 participants