JDK-8100602 : Need to remove existing Alert class
  • Type: Enhancement
  • Component: javafx
  • Sub-Component: graphics
  • Affected Version: fx2.0
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2011-04-18
  • Updated: 2015-06-16
  • Resolved: 2011-04-27
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
fx2.0Fixed
Related Reports
Duplicate :  
Duplicate :  
Relates :  
Description
We currently have an Alert class with some static convenience methods defined.

This class is not currently functional at all on Prism. In addition to the changes needed to make it functional, the current "Toolkit-based" implementation is not flexible (cannot be skinned), is based on an old JavaFX-TV implementation, and has introduced a dependency in javafx-ui-quantum on javafx-ui-controls. It needs to be rewritten.

Additionally, the public Alert API is missing a necessary parameter for the owner of the dialog.

I have prototyped an updated version of the API (by adding the missing "owner" parameter) and a bare-bones sample implementation in toys/HelloWorld/alertdialog that can be the basis of a real implementation.

We need to do one of the following:

1) Remove Alert and don't provide the functionality at all in this release. This is the easiest, but we would not be providing something that was there (after a fashion) in JavaFX 1.3.

2) Move Alert to javafx.scene.control and fix up the API by adding the missing Window owner parameter to all of the methods. Implement a placeholder implementation, initially with no UI design. The problem is it will be a late-breaking feature and doing the UI design is not scheduled work. I had also wondered whether we could make it "preview" control for 2.0, but Rich thinks this may not fly.

Both options will include removing javafx.stage.Alert and the toolkit implementations (which, as noted above, are not functional anyway).

Comments
http://jfxsrc.us.oracle.com/javafx/presidio/scrum/graphics/jfx/rev/2c3738a4fc65 http://jfxsrc.us.oracle.com/javafx/presidio/scrum/graphics/apps/rev/86be14342786 http://jfxsrc.us.oracle.com/javafx/presidio/scrum/graphics/runtime/rev/123b6ea87080
27-04-2011

Webrev: http://beethoven.us.oracle.com/webrev/javafx/rt-12638-v2/
23-04-2011

This JIRA will track the "remove" part of the equation. I will file a separate "Consider creating a javafx.scene.control.Alert class" JIRA.
18-04-2011

This needs to be done by beta.
18-04-2011