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

Common commands are not available in the dropdown #6930

Closed
skabashnyuk opened this issue Oct 24, 2017 · 6 comments
Closed

Common commands are not available in the dropdown #6930

skabashnyuk opened this issue Oct 24, 2017 · 6 comments
Labels
kind/bug Outline of a bug - must adhere to the bug report template.

Comments

@skabashnyuk
Copy link
Contributor

Description

Common commands are not available in the drop-down. Stack che-in-che.
2017-10-24 09 03 05

@skabashnyuk skabashnyuk added kind/bug Outline of a bug - must adhere to the bug report template. target/che6 labels Oct 24, 2017
@azatsarynnyy
Copy link
Member

FYI EXEC drop-down displays running processes but not the commands )

@vparfonov
Copy link
Contributor

vparfonov commented Dec 11, 2017

@slemeur What do you think about that, looks like current implementation of command/process panel not clear for user?

@slemeur
Copy link
Contributor

slemeur commented Dec 11, 2017

I believe there is a "Run" and a "Debug" buttons with a small dropdown too, which are most natural place to do those actions.

Here the confusion is mostly due to way commands were handled in the past.

Still, there are few things we can do to improve:

  • The placeholder "Ready - Start command" can be misleading. We can have a better language like "Ready - Hit Run, Debug or Browse All to start a command".
  • When there is no command running, we could display a message first row in the dropdown "Nothing running".
  • The last item of the dropdown is "Create new command", I think we can add another item "Browse commands"

@slemeur
Copy link
Contributor

slemeur commented Dec 11, 2017

@azatsarynnyy WDYT ?

@azatsarynnyy
Copy link
Member

I also think that the problem is the misleading placeholder "Start command".
We should tell the user somehow that EXEC drop-down displays the currently running commands (and those which were run) but not all existing ones.
The placeholder with the text like "Nothing running" should be much better and enough I guess.

@skabashnyuk
Copy link
Contributor Author

I propose to close this issue because I actually don't correctly understand the concept.
We have a right issue with an improvement of that entire place. #4993 I propose to move commenting there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Projects
None yet
Development

No branches or pull requests

4 participants