Skip to content

Read splash shell title directly from the product in IDEApplication#3923

Open
vogella wants to merge 1 commit intoeclipse-platform:masterfrom
vogella:fix/ide-splash-title-direct-product
Open

Read splash shell title directly from the product in IDEApplication#3923
vogella wants to merge 1 commit intoeclipse-platform:masterfrom
vogella:fix/ide-splash-title-direct-product

Conversation

@vogella
Copy link
Copy Markdown
Contributor

@vogella vogella commented Apr 22, 2026

Summary

IDEApplication.start used ChooseWorkspaceDialog.getWindowTitle() to set the splash shell's taskbar title. That helper belongs to the workspace chooser dialog: it returns Platform.getProduct().getName() with a fallback to IDEWorkbenchMessages.ChooseWorkspaceDialog_defaultProductName, an NLS string tied to the chooser dialog's presentation.

The splash shell is owned by the application, not the chooser dialog, and the dialog's NLS fallback is not appropriate for a splash taskbar entry. This change reads the product name directly in IDEApplication. When no product is configured, the launcher's default title is kept.

ChooseWorkspaceDialog.getWindowTitle() is kept for use inside the chooser dialog itself.

Behavior

For Eclipse IDE products, which always have a product name, the taskbar text on the splash shell is unchanged. For applications without a configured product, the launcher's default title is preserved instead of being replaced by a chooser-dialog placeholder.

Test plan

  • Start an Eclipse IDE build; splash taskbar entry shows the product name as before.
  • Start a minimal RCP application without a configured product; launcher's default title remains.
  • Workspace chooser dialog title is unaffected (still uses ChooseWorkspaceDialog.getWindowTitle() internally).

IDEApplication.start set the splash shell's taskbar title via
ChooseWorkspaceDialog.getWindowTitle(). That helper is scoped to the
workspace chooser dialog: it returns Platform.getProduct().getName(),
and falls back to an IDEWorkbenchMessages string whose name
(ChooseWorkspaceDialog_defaultProductName) is tied to the chooser
dialog's presentation.

Using it for the splash shell is a layering inversion. The splash is
a property of the application, not of the chooser dialog, and the
dialog-specific NLS fallback is not appropriate for the splash
taskbar entry.

Read Platform.getProduct().getName() directly in IDEApplication. If
no product is configured, leave the launcher's default title in place
rather than substituting a chooser-dialog placeholder.
ChooseWorkspaceDialog.getWindowTitle() is retained as an internal
helper for the dialog itself.

No user-visible change for Eclipse IDE products, which always have a
product name configured.
@github-actions
Copy link
Copy Markdown
Contributor

Test Results

   852 files  ±0     852 suites  ±0   59m 6s ⏱️ + 4m 3s
 7 911 tests ±0   7 668 ✅ ±0  243 💤 ±0  0 ❌ ±0 
20 235 runs  ±0  19 580 ✅ ±0  655 💤 ±0  0 ❌ ±0 

Results for commit 2b8ab6d. ± Comparison against base commit 64aecb7.

@vogella vogella marked this pull request as ready for review April 22, 2026 13:59
@vogella vogella requested a review from Copilot April 22, 2026 14:01
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates IDEApplication startup behavior so the splash shell’s taskbar title is sourced directly from the configured Eclipse product (when present), avoiding reuse of the workspace chooser dialog’s UI-specific fallback.

Changes:

  • Set splash shell taskbar title from Platform.getProduct().getName() when a product is configured.
  • Preserve the launcher-provided default splash title when no product is configured (instead of using the chooser dialog’s placeholder).
  • Keep the splash shell icon assignment via Window.getDefaultImages().

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@BeckerWdf
Copy link
Copy Markdown
Member

@vogella: What kind of problem do you want to solve with this PR? Can you pls. explain?

@vogella
Copy link
Copy Markdown
Contributor Author

vogella commented Apr 22, 2026

The splash shell is owned by the application, not the chooser dialog, and the dialog's NLS fallback is not appropriate for a splash taskbar entry.

It also triggers unnecessary class loading even if the dialog is not shown, like in a restart

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.

3 participants