JDK-8101235 : Rewrite prism-es2 pipeline to not use OpenGL bindings
  • Type: Enhancement
  • Component: javafx
  • Sub-Component: graphics
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2012-01-19
  • Updated: 2015-06-16
  • Resolved: 2012-05-24
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.
JDK 7
7u6Fixed
Related Reports
Blocks :  
JDK-8128280 - Big footprint of es2 pipeline on mac
Blocks :  
JDK-8101075 - Reduce prism-es2 memory footprint
Blocks :  
JDK-8091086 - Implement performance counters (prism.printStats) feature for prism-es2 pipe
Blocks :  
JDK-8100754 - isSupported Capabilities support
Blocks :  
JDK-8115085 - Gtk: Glass should honor the contract of only use the VisualID, passed in from Prism, to create window
Duplicate :  
JDK-8101075 - Reduce prism-es2 memory footprint
Relates :  
JDK-8100620 - The demise of JOGL
Relates :  
JDK-8098102 - Glass should not be the owner of graphics context (Glass client should be the owner)
Description
In 2.1 we refactored prism-jogl and eliminated it as a separate entity. In 2.2 we need to rewrite the prism-es2 pipeline to be more like the prism-d3d pipeline with a similar native interface. This will reduce complexity and may help reduce the differences between D3D and OpenGL pipelines. It will also help with the static footprint of JavaFX.
Comments
Closed-unverified. An internal change with no unit test provided
11-07-2012
Need to factor in isSupported functionality in the re-write.
06-03-2012
Set priority to Major as this is an important feature for 2.2 and this work needs be done earlier in the development phase.
06-03-2012
Agreed. I'm ok with this EFP
06-02-2012
This does not affect the public API nor should there be any application-visible behavioral differences. As such, it should not require any new tests to be written. SQE should only need to very that there are no regressions in existing functionality.
04-02-2012
Implements A360 Feature http://oracleplan.oracle.com/gotoEntity?entityType=FEATURE&entityId=769577
19-01-2012