Bug 199254

Summary:	add status support for all editors
Product:	[Eclipse Project] Platform	Reporter:	Rodrigo Peretti <rodrigo>
Component:	UI	Assignee:	Boris Bokowski <bokowski>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	daniel_megert, emoffatt
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Rodrigo Peretti

2007-08-08 10:05:24 EDT

The StatusTextEditor has the nice feature of displaying a status when things go wrong. My request is basically to have that feature provided higher up in the hierarchy and not just limited to text editors. It would be nice to have that in graphical editors too (the canvas could be replaced by the status composite).

So what I'd like to see is a StatusEditor or maybe just a public helper class somewhere that creates the status composite. It would be great to have consistent error reporting across all editors.

Comment 1 Eric Moffatt

2007-08-08 10:43:58 EDT

Passing on to Text for initial comment...

Comment 2 Dani Megert

2007-08-08 10:47:13 EDT

Well, text editors already support this. The request is to offer similar support for all kinds of editors.

Comment 3 Eric Moffatt

2007-08-08 10:51:24 EDT

Daniel, I understand. I'm trying to get a feel for how problemmatic such a split might be (i.e. how hard is it to split the code to support the 'status' management independent of the actual editor)?

Comment 4 Dani Megert

2007-08-08 10:58:43 EDT

Sure. Just cc me in such a case. No need to move the bug ;-)

We simply use a StackLayout and then switch between the real content and the status page.

Comment 5 Eric Moffatt

2007-08-10 11:18:33 EDT

Boris? This looks to have both API and EditorMgmt issues...

Comment 6 Eclipse Webmaster

2019-09-06 15:35:30 EDT

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.