[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[eclipse-pmc] Re: PMC API request: two new constructors in WorkbenchStatusDialogManager plus deprecation of existing
|
+1 to adding the new constructors.
I too dislike the idea of releasing constructors already marked as deprecated, but unless you can *prove* that there are no consumers of them, it's simply too late to remove them.
McQ.
Kevin McGuire---05/15/2008 03:03:34 PM---GOALS/BENEFITS: WorkbenchStatusDialogManager was introduced in 3.4 but the constructors took a Shel
![]()
From: | ![]()
Kevin McGuire/Ottawa/IBM |
![]()
To: | ![]()
eclipse-pmc@xxxxxxxxxxx |
![]()
Cc: | ![]()
Mike Wilson/Ottawa/IBM@IBMCA, Tod Creasey/Ottawa/IBM@IBMCA, Szymon Brandys/Poland/IBM@IBMPL |
![]()
Date: | ![]()
05/15/08 03:03 PM |
![]()
Subject: | ![]()
PMC API request: two new constructors in WorkbenchStatusDialogManager plus deprecation of existing |
GOALS/BENEFITS:
WorkbenchStatusDialogManager was introduced in 3.4 but the constructors took a Shell argument that they should not have. The shell is now being ignored in WorkbenchStatusDialogManager due to other fixes already released.
This proposal is simply to:
1) Add new constructors that don't take the shell so people can the "correct" API
2) Mark the two existing constructors as deprecated (as much as it pains us
to do so in a newly released class).
ASSOCIATED BUGS:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=231163
RISKS:
None, this is new API in a new class.
Also the two early adopters that we know of of the new status handling support aren't using it.
PERFORMANCE IMPACT:
none
DESCRIPTION:

