Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Console and Search views: use a distinct part name per view instance

未关闭
#3,000 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
java
领域
desktop

调研方向

Start with ConsoleView and SearchView, and compare how TerminalsView::createPartControl derives a name from IViewSite::getSecondaryId. The issue offers two options (secondary-id numbering or asking the user for a name, as the Problems view does) and does not choose one, so settle that with maintainers first. Done means each open instance of these views gets a distinct part name.

由索引模型根据 Issue 内容生成。

描述

enhancement

Let's make sure issue is not already fixed in latest builds first.

Suggestion

When several Console or Search views are open, their tabs all show the same name, so they can't be told apart:

Image

The screenshot shows multiple [Console / Search] views with identical tab names, next to Terminal and Problems views, which each handle this in their own way.

Proposal

Give each instance of ConsoleView and SearchView a distinct part name. There are two existing patterns to follow:

  1. Numbered names, as in the Terminal view. Derive the name from the IViewSite::getSecondaryId when one is present, in the same way TerminalsView::createPartControl does. This needs no user interaction.
  2. User-provided names, as in the Problems view. Ask the user for a name when an additional view is opened. This gives more meaningful names, at the cost of an extra step.

Related

Once https://github.com/eclipse-platform/eclipse.platform.ui/pull/4459 is merged, the Ctrl+F7 view switcher will show whatever part name a view sets, so distinct names would make these views distinguishable there as well.

Community

  • I understand suggesting an enhancement doesn't mandate anyone to implement it. Other contributors may consider this suggestion, or not, at their own convenience. The most efficient way to get it fixed is that I implement it myself and contribute it back as a good quality patch to the project.
主要语言
Java
星标
165
派生
174
平均合并
2 天 17 小时
30 天内合并 PR
43

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

eclipse-platform/eclipse.platform 的其他 Issue

查看 eclipse-platform/eclipse.platform 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。