Bug 324233

Summary: [Dialogs] new IconAndMessageAndDetailsDialog implementation extends IconAndMessageDialog
Product: [Eclipse Project] Platform Reporter: Kirk Beitz <kirk.beitz>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: P3 CC: daniel_megert, markus.kell.r, remy.suen
Version: 3.7Flags: kirk.beitz: review?
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
IconAndMessageAndDetailsDialog.java (extends IconAndMessageDialog.java) kirk.beitz: review?

Description Kirk Beitz CLA 2010-09-01 14:32:10 EDT
Created attachment 177994 [details]
IconAndMessageAndDetailsDialog.java (extends IconAndMessageDialog.java)

There are times when eclipse plug-ins need to report errors, warnings, or other information from external tools where the information is imperative enough to require a generic dialog.

For cdt edc, we found ErrorDialog almost did what we wanted, but under the hood, with it's use of SWT.List to describe each line of a problem stack, it is clearly detailed to one particular use.

We started to attempt to override ErrorDialog by replacing only the calls that populated the SWT.List, but there's a final restriction on one important function that accesses a private member, so such an override is simply not possible.

To provide what we need, internal to edc, we've implemented IconAndMessageAndDetailsDialog .

We have a version that has Javadoc and stripped of anything that isn't pulled in by ErrorDialog so that it can be promoted to org.eclipse.jface.dialogs, if there is interest.

This version uses SWT.Text so that (for example) the edc debug agent can report back an error that may have no stack information, but may have a multi-line log of the error that occurred on the remote target.

The attached file is the new class for jface, if interested.

There's no immediate need for this, as we have implemented this internal to edc for now.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:18:20 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.