Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
#3,000 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
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日 16時間
マージ済み PR(30日)
45

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

eclipse-platform/eclipse.platform のほかの issue

eclipse-platform/eclipse.platform の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。