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

Users can select the editor when starting an example from Che Dashboard #20627

Closed
l0rd opened this issue Oct 12, 2021 · 11 comments · Fixed by eclipse-che/che-dashboard#575
Closed
Assignees
Labels
area/dashboard area/ux Issues related to User Experience Design kind/enhancement A feature request - must adhere to the feature request template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system. sprint/current

Comments

@l0rd
Copy link
Contributor

l0rd commented Oct 12, 2021

Is your enhancement related to a problem? Please describe

When a user select a quick start (sample or URL) he cannot choose the editor that will be used in the workspace.

Describe the solution you'd like

Having an editor dropdown list in the dashboar Getting Started page to select the specific editor. cc @beaumorley

Release Notes Text

When starting a workspace from Che samples page in user dashboard it's possible to select the editor that will be included in the development environment.

@l0rd l0rd added the kind/enhancement A feature request - must adhere to the feature request template. label Oct 12, 2021
@l0rd l0rd added area/dashboard severity/P1 Has a major impact to usage or development of the system. labels Oct 12, 2021
@sleshchenko sleshchenko added area/ux Issues related to User Experience Design status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. labels Oct 21, 2021
@sleshchenko
Copy link
Member

Added UX label since it's something that needs a design proposal from UX Team.

@max-cx
Copy link

max-cx commented Nov 16, 2021

The outcome will require new content for the docs, correct?

Do we already know which SME will draft the new content?

@che-bot
Copy link
Contributor

che-bot commented May 15, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 15, 2022
@che-bot che-bot closed this as completed May 22, 2022
@l0rd l0rd added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 30, 2022
@l0rd l0rd reopened this May 30, 2022
@olexii4 olexii4 self-assigned this Jul 5, 2022
@olexii4
Copy link
Contributor

olexii4 commented Jul 7, 2022

I have prepared a video https://youtu.be/E9ix6h2bIfc for UX feedback.

@beaumorley
Copy link

HI @olexii4 Thanks for sharing the video. It looks great. A few suggestions.

1.) It would be nice to give the user a little more info on what they are doing to compliment the tooltip that gives more info on the editor. There is a title options for a dropdown you could use. Like this:
image

2.) You could also indicate the editor that is already selected. Like this:
image

3.) If you wanted to not have the tooltip on rollover, you could also add the icon next to each editor (if they each have a distinct icon that would help the user understand what they are). If that interested you, I could help figure out the icons.

I have a design meeting with my team tomorrow. I will LYK if they have more ideas.

@l0rd
Copy link
Contributor Author

l0rd commented Jul 8, 2022

Thank you @beaumorley that's great.

@olexii4
Copy link
Contributor

olexii4 commented Jul 11, 2022

@beaumorley I have some proposals:
Знімок екрана 2022-07-11 о 02 52 53
Знімок екрана 2022-07-11 о 02 53 09
Знімок екрана 2022-07-11 о 02 53 27
I have added the 'next' tag icon.
WDYT?

PS
A variant with additional editors:
Знімок екрана 2022-07-12 о 17 00 09

@l0rd
Copy link
Contributor Author

l0rd commented Jul 12, 2022

@olexii4 I like the next icon but I am confused: if I am using a nightly Che I will have next editors and if I am using stable Che I expect to see stable editors. I would not provide too many options to developers.

@olexii4
Copy link
Contributor

olexii4 commented Jul 13, 2022

@l0rd The latest variant:
Знімок екрана 2022-07-13 о 13 57 18

@ibuziuk
Copy link
Member

ibuziuk commented Jul 13, 2022

@beaumorley could you please review - eclipse-che/che-dashboard#575
would be great to get your approval before merging ;-)

@beaumorley
Copy link

@ibuziuk LGTM. Thank you!

@l0rd l0rd added new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording and removed status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. labels Jul 21, 2022
@l0rd l0rd changed the title A user should be able to select an alternative editor from the dashboard Users can select the editor when starting an example for Che dasboard Jul 21, 2022
@l0rd l0rd changed the title Users can select the editor when starting an example for Che dasboard Users can select the editor when starting an example for Che Dashboard Jul 21, 2022
@l0rd l0rd changed the title Users can select the editor when starting an example for Che Dashboard Users can select the editor when starting an example from Che Dashboard Jul 21, 2022
@max-cx max-cx removed the status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording label Jan 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard area/ux Issues related to User Experience Design kind/enhancement A feature request - must adhere to the feature request template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system. sprint/current
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants