Skip to content

Use "(running)" text instead of Unicode symbol for active launch indicator - #2934

Open
BeckerWdf wants to merge 2 commits into
eclipse-platform:masterfrom
BeckerWdf:feature/launch-running-indicator
Open

BeckerWdf wants to merge 2 commits into
eclipse-platform:masterfrom
BeckerWdf:feature/launch-running-indicator

Conversation

@BeckerWdf

@BeckerWdf BeckerWdf commented Sep 16, 2026

Copy link
Copy Markdown
Member

Summary

  • Replaces the Unicode symbol with the text (running) as the indicator for active launch configurations in the launch history menu.
  • The text label is more accessible and avoids potential font/rendering issues with Unicode symbols.

Test plan

  • Open the launch history dropdown while a launch configuration is running
  • Verify the entry shows My Config (running) instead of My Config ⚙
  • Verify terminated launches no longer show the indicator

Fixes #2933

Show "(running)" suffix instead of a Unicode symbol next to active
launch configurations in the launch history menu.

Fixes eclipse-platform#2933
@BeckerWdf

Copy link
Copy Markdown
Member Author

Looks like this now:
Screenshot 2026-09-16 at 12 10 36

@BeckerWdf

Copy link
Copy Markdown
Member Author

@SougandhS: What do you think?

@BeckerWdf BeckerWdf self-assigned this Sep 16, 2026
@SougandhS

Copy link
Copy Markdown
Contributor

(running) adds noticeable width to every entry in the launch history menu, especially with longer config names, it could crowd the dropdown... doesn't feel like an indicator anymore..

@BeckerWdf

Copy link
Copy Markdown
Member Author

(running) adds noticeable width to every entry in the launch history menu, especially with longer config names, it could crowd the dropdown... doesn't feel like an indicator anymore..

That's a valid point.

@iloveeclipse

Copy link
Copy Markdown
Member

IMO original idea was looking better.
Maybe you should start a poll to check whether we should change it or not as proposed here, let community decide.
Ideally provide screenshots before / after so it is clear for everyone what we are talking about.

@github-actions

Copy link
Copy Markdown
Contributor

Test Results

    54 files  ±0      54 suites  ±0   58m 19s ⏱️ - 1m 15s
 4 810 tests ±0   4 788 ✅ ±0   22 💤 ±0  0 ❌ ±0 
12 321 runs  ±0  12 168 ✅ ±0  153 💤 ±0  0 ❌ ±0 

Results for commit fde13d3. ± Comparison against base commit 2d15cf3.

@akurtakov

akurtakov commented Sep 16, 2026

Copy link
Copy Markdown
Member

The one with running looks quite wrong on my Linux system (in addition to concerns about width)
image
so I also vote for keeping the symbol one.

@merks

merks commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

I liked the symbol too. It's very concise...

@BeckerWdf

Copy link
Copy Markdown
Member Author

The one with running looks quite wrong on my Linux system (in addition to concerns about width) image so I also vote for keeping the symbol one.

It misses a whitspace. Is that what you mean with "wrong"?

@BeckerWdf

Copy link
Copy Markdown
Member Author

IMO original idea was looking better.

your mean the "gear"?

@iloveeclipse

Copy link
Copy Markdown
Member

your mean the "gear"?

Yes. Current master state.

@HeikoKlare

Copy link
Copy Markdown
Contributor

I have to admit that I quite dislike the gear. It took me a while to understand what that symbol is supposed to tell me.
I got used to it though, and I also understand the arguments regarding width when adding a "(running)" suffix to the entry label. So this is not an opinion for or against anything. I just want to second the concerns regarding accessibility (and comprehensibility) of the current symbol.

@jasmin261098

Copy link
Copy Markdown

I agree that an Icon does look better than writing out the word "running".

But I have to point out, that an emoji is not a valid eclipse IDE icon. A user can see major differences in the intended look and feel of the IDE, plus emojis look different on different operating systems and are inappropriate for a professional software as Eclipse.

I would suggest to use existing solutions for this use case. For example you could use the base "java_app.svg" Icon and add an OVR icon on top of it, like the "run_co.svg" Icon.

image

I currently work on the eclipse Icons myself and with a bachelor degree in graphic design I would like to help solve this issue.

@akurtakov

Copy link
Copy Markdown
Member

It misses a whitspace. Is that what you mean with "wrong"?

That is one thing but it also looks like something I have put in the launch configuration name myself e.g. I have launches "Eclipse Gtk4 X11 IBus" so "(running)" I take as part of the name.

@akurtakov

akurtakov commented Sep 16, 2026

Copy link
Copy Markdown
Member

FWIW, the "gear" is overcomplicated for the purpose and an indicator I take for "setup" not for "running" , a • (https://en.wikipedia.org/wiki/Bullet_(typography) ) fits better as it was proposed somewhere, maybe even initially.

@BeckerWdf

Copy link
Copy Markdown
Member Author

I would suggest to use existing solutions for this use case. For example you could use the base "java_app.svg" Icon and add an OVR icon on top of it, like the "run_co.svg" Icon.

image

I just locally implemented what proposal.

Looks like this:

Screenshot 2026-09-17 at 09 01 57 Screenshot 2026-09-17 at 09 01 34

What's your opinion on that proposal?

@SougandhS

SougandhS commented Sep 17, 2026 via email

Copy link
Copy Markdown
Contributor

@BeckerWdf

BeckerWdf commented Sep 17, 2026

Copy link
Copy Markdown
Member Author

Thanks, similar was proposed earlier See #2652 (comment) & #2652 (comment) Get Outlook for Androidhttps://aka.ms/AAb9ysg

So why was is not implemented? What have been the reasons?

@BeckerWdf

Copy link
Copy Markdown
Member Author

Just discovered that a tooltip is added for not running launch configs like this:
Screenshot 2026-09-17 at 09 22 42

Why not adding a tooltip for running ones too:
Screenshot 2026-09-17 at 09 19 08

@merks

merks commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

I wonder how it looks with external tools launches which have the little red toolbar button in the lower right?

@SougandhS

SougandhS commented Sep 17, 2026 via email

Copy link
Copy Markdown
Contributor

@BeckerWdf

Copy link
Copy Markdown
Member Author

Tooltip will require hovering and take 1-3 seconds to show up, with gear indicator users can quickly identify the running launches without hovering and waiting

I mean in addition - not as replacement for the "indicator".

@BeckerWdf

Copy link
Copy Markdown
Member Author

I wonder how it looks with external tools launches which have the little red toolbar button in the lower right?

you mean this:
image

@SougandhS

Copy link
Copy Markdown
Contributor

I mean in addition - not as replacement for the "indicator".

That would be great :D

@BeckerWdf

Copy link
Copy Markdown
Member Author

I mean in addition - not as replacement for the "indicator".

That would be great :D

Ok. I will provide a separate PR for that as it's independent from the "indicator" discussion.

@BeckerWdf

Copy link
Copy Markdown
Member Author

I mean in addition - not as replacement for the "indicator".

That would be great :D

Ok. I will provide a separate PR for that as it's independent from the "indicator" discussion.

see: #2937

@akurtakov

Copy link
Copy Markdown
Member

As discussion here has went in full circle I believe it's time to have a poll with all possible options and let the majority decide what is best.
Regarding overly icon alternative - this is really good option for limited scope product and not that good idea at all for generally extensible platform . E.g. imagine run config for plugin with mostly green icon (a top ten MPC download is such https://github.com/cucumber/cucumber-eclipse/wiki/Feature-Runner), color blindness and etc. and green "indicator" - the indicator will be totally lost .

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

Successfully merging this pull request may close these issues.

UX of "Running Indicator" for Launch Configurations should be improved

7 participants