JDK-8099875 : Add 3D transformations to the JavaFX API
  • Type: Sub-task
  • Component: javafx
  • Sub-Component: graphics
  • Affected Version: fx1.2
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2009-03-10
  • Updated: 2015-06-16
  • Resolved: 2009-12-16
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
fx1.3Fixed
Related Reports
Blocks :  
JDK-8099877 - Add Z values to Bounds API to support 3D
Blocks :  
JDK-8099878 - Implement rendering for all 3D transformed primitives
Blocks :  
JDK-8099456 - Create "Perspective Transformation Node" in the scene graph
Blocks :  
JDK-8099419 - Add Z depth sorting (Z-buffering) to JavaFX
Blocks :  
JDK-8099880 - Resolve grouping semantic for opacity or effects with 3D transforms
Description
We need to add 3D transformations to the javafx.scene.transform classes such that:

1) 2D-only applications need not specify or even know about 3D (reasonable defaults for everything)

2) An application that uses only 2D transforms will render the same as today with no source code changes

3) Allow for easy mixing of 2D and 3D transforms

Note that whatever we do for soma must be done in a manner that future versions will be backward compatible with soma.
Comments
In order to implement this, we have some decisions to make: 1) What profile will the new API be part of? Probably desktop for Marina, but need to finalize that decision 2) Will we actually implement 3D transforms for the existing AWT/Java2D stack? If so, how? Using the perspective effect under-the-covers? What are the performance implications of doing this?
10-03-2009