JDK-8090399 : Rewrite (AA)TessShapeRep classes in order to avoid unnecessary translations
  • Type: Enhancement
  • Component: javafx
  • Sub-Component: graphics
  • Affected Version: 8
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2012-10-17
  • Updated: 2018-09-05
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
tbdUnresolved
Related Reports
Relates :  
JDK-8108358 - Prism: no antialiasing when rendering shapes with a 3D transform
Description
(AA)TessShapeRep classes move shapes before rendering them and then translate them back to the original place. This may cause issues with non-proportional gradients (as suggested by a TODO in the code).
We should be able to get rid of the translation and shape manipulation, as ShapeRep should be provided with the current geometry of the shape.
Comments
RT-17396 wouldn't handle 3D transforms, though (that would require something like Loop-Blinn or similar technique). The plan of record is to do what you mentioned in your first comment: nuke the tessellator, render into a texture, and transform the image in 3D (using auto-mipmap generation and anisotropic filtering). See RT-5534.
31-05-2013
Unless we used something like RT-17396, in which case we still wouldn't need tessellation but we could also avoid using a texture when going 3D
30-05-2013
I think we've even talked about nuking all tessellation all together. Instead we'll just render to texture when a 2D thing goes into 3D. This should be faster and simpler.
30-05-2013