Community
Participate
Working Groups
This feature is used for tracking the proposed support for managing messages in message containers such as Form, WizardPage, TitleAreaDialog etc. The design is described in the attached proposal.
Created attachment 55992 [details] A proposal for message manager
Created attachment 55993 [details] The initial implementation (matches 3.3M4-level of JFace).
The attached patch provides the baseline implementation of the proposal. It also fixes a bug in ControlDecoration whereby size for the multi-line descriptions was correctly computed but only first line was actually painted (wrong SWT method).
Created attachment 55994 [details] A patch for org.eclipse.ui.forms.examples project with an example.
How to play with the provided implementation: 1) Check out org.eclipse.jface from HEAD 2) Apply the JFace patch 3) Check out org.eclipse.ui.forms from HEAD 4) Apply the example patch 5) Launch another Eclipse 6) Select 'Window>Customize Perspective>Commands>Eclipse Forms Examples' action set. 7) Select 'Form Editors>Simple Form Editor' from the main menu 8) Switch to the 'Message Manager' tab
Created attachment 56010 [details] Patch for org.eclipse.ui.forms Forgot to add the necessary required patch for org.eclipse.ui.forms.
In the steps above, you will need to apply examples patch to org.eclipse.ui.forms.example project, and the newly attached forms patch to org.eclipse.ui.forms project. Sorry for the confusion.
I will look this over for M6.
For all practical purposes, I have deferred this proposal for 3.3 and implemented the proposal in the more limited context of the UI Forms (see http://www.eclipse.org/eclipse/platform-ua/proposals/forms/enhancements-3.3/index.html). The long-term strategy should still be to have a general approach that works in similar contexts.
ok, I'll remove a milestone and we can take this up in a more general form later.
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
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.