-
Enhancement
-
Resolution: Unresolved
-
P3
-
fx2.0
It seems like a tonne of busy work is going on in some classes, for example, Region, where it is doing a lot of translating from .region package classes to .sg package classes, despite the fact that they are now both Java, and seem to be largely equivalent. It may be possible that we can use the 'FX' API classes in the scenegraph as well, now that it is all in Java.
I imagine, based on how thoroughly Region is used (and the extent of busy-work that is being performed within Region), that if this were the case we could reap considerable performance gains.
Areas to consider:
* Duplication between .region and .sg classes
* Classes such as Color (From Rich: "prism could potentially take Colors directly rather than converting those too")
I imagine, based on how thoroughly Region is used (and the extent of busy-work that is being performed within Region), that if this were the case we could reap considerable performance gains.
Areas to consider:
* Duplication between .region and .sg classes
* Classes such as Color (From Rich: "prism could potentially take Colors directly rather than converting those too")