Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 13991

Summary:	[Contributions] [Services] A site should provide access to a parts input element
Product:	[Eclipse Project] Platform	Reporter:	Dirk Baeumer <dirk_baeumer>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P5	CC:	douglas.pollock, mistria, remy.suen, sxenos
Version:	2.0	Keywords:	helpwanted
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Dirk Baeumer

2002-04-17 09:11:29 EDT

Build 20020416

A IWorkbenchSite give access to a selection provider and therefore to the 
current selection of an editor, view part or page. But a site can not be used 
to access an editor's, view part's or page input element. As a consequence the 
JDT actions which work on selections and the input element (like most of the 
source actions) have to keep a reference to a site and one to the editor to 
access the input element.

The action could be written simplier if the site would give access to the input 
element as well.

Comment 1 Nick Edgar

2002-04-17 09:39:20 EDT

There is no notion of input for views currently in the workbench.
The notion of page input is being replaced with working set.

Comment 2 Nick Edgar

2002-04-17 09:40:11 EDT

I agree there should be more commonality in the interfaces for contributions, 
but this will not change for 2.0.
Defering.

Comment 3 Randy Giffen

2002-08-09 16:22:13 EDT

Reopen to investigate

Comment 4 Douglas Pollock

2004-11-01 13:08:18 EST

Re-assigning to Stefan to look at with his services work (?).

Comment 5 Michael Van Meekeren

2006-04-21 13:56:50 EDT

Moving Dougs bugs

Comment 6 Paul Webster

2007-04-05 19:01:32 EDT

Assigning to component owner
PW

Comment 7 Lars Vogel

2019-11-27 07:37:36 EST

This bug hasn't had any activity in quite some time. Maybe the problem got
resolved, was a duplicate of something else, or became less pressing for some
reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it.
The information can be, for example, that the problem still occurs, that you
still want the feature, that more information is needed, or that the bug is
(for whatever reason) no longer relevant.

If the bug is still relevant, please remove the stalebug whiteboard tag.