Enhancements to 3D for JFX9?

Tom Schindl tom.schindl at bestsolution.at
Fri Apr 24 18:41:59 UTC 2015


I never proposed to rely on this feature forever but to relax the
concerns raised that JDK9 is the end for useing JavaFX in new not yet
explored ways and people stop using it today because it is already sure
today that you won't get the API you require in your app.

I've already outlined in our EclipseCon meeting with Mark and Alex how
one could go for allowing none global access to not yet finished APIs
without useing the big hammer -XX.... - Eclipse with its @noimplement
and @noextend and Equinox with it's private-package exports show you
ways how this could be address so that eg JavaFX could expose some of
its internal stuff in JKD9.

I think something like that is essential for young modules like javafx.


On 24.04.15 17:27, Donald Smith wrote:
> Yes, but then read the rest of the thread.  You really must not rely on
> the theoretical possibility of an XX flag that magically kicks all your
> problems down the road a year or two.  The best time to get all this
> nailed correctly is now.  That flag is not likely to be as extensive and
> durable as everyone is imagining.
>  - Don
> On 24/04/2015 8:19 AM, Tom Schindl wrote:
>> Did you read the reply from Phil in the other thread?
>>> There will be a -XX flag in JDK 9 that jigsaw provides to aid in the
>>> transition.
>> So you will not have to maintain a JDK9 build but only start with this
>> thread to still access private APIs and this is something you can
>> clearly control if you install the JDK with your app!
>> Tom
>> On 24.04.15 14:05, Robert Krüger wrote:
>>> On Fri, Apr 24, 2015 at 1:16 PM, Mike Hearn <mike at plan99.net> wrote:
>>>> this may mean, people who do this must work with a patched JDK in the
>>>>> future.
>>>> Right. But I think that's going to be more and more common in
>>>> future. If
>>>> you rely on people installing proprietary stuff like JWS or applets
>>>> then
>>>> it's a bleak future, as the way forward is clearly bundled JREs.
>>> patched != bundled. For us this would be quite a step back, having to
>>> maintain our JDK patches/builds. Bundling itself is fine in our business
>>> cases.

Thomas Schindl, CTO
BestSolution.at EDV Systemhaus GmbH
Eduard-Bodem-Gasse 5-7, A-6020 Innsbruck
Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck

More information about the openjfx-dev mailing list