Project Proposal: JFX
Richard Bair
richard.bair at oracle.com
Fri Oct 28 06:37:20 UTC 2011
Ok thanks for clarifying. So OpenJDK is made up of multiple projects. One of those is JDK 7 for example, or JDK 8. These projects form the RI. In addition you have projects like VisualVM which are not themselves part of the standard, yet are part of OpenJDK. Then there are other projects like Coin and Lambda which are part of OpenJDK, and also have associated JSR's from which some, or all, of their code will be "promoted" into the core JDK through the JCP process. We hope JavaFX will be like one of these. As I mentioned in my initial post, we hope to have a JSR for JavaFX in the Java 9 timeframe. In other words, we want to incubate JavaFX in OpenJDK precisely because we would like to see it become part of the standard. Of course we cannot unilaterally make those sorts of decisions, it depends on the JCP and the community as to whether they want JavaFX to be standardized, but that is certainly our hope.
In the meantime, this does not dilute the role of OpenJDK as the RI for the Java platform.
Thanks
Richard
On Oct 27, 2011, at 11:23 PM, Frans Thamura <frans at meruvian.org> wrote:
> my mind said.. that openjdk is based on standard, it become RI
> implementation of Java SE,
>
> CMIIW
>
> and JFX is not standard product,
>
> what happen if JFX relaease with OJDK? will it break the RI approach
>
> that is the area i am concering
>
> F
>
>
>
> On Fri, Oct 28, 2011 at 1:20 PM, Richard Bair <richard.bair at oracle.com> wrote:
>> I'm sorry Frans, I'm afraid I didn't understand that.
>>
>> Thanks
>> Richard
>>
>> On Oct 27, 2011, at 10:43 PM, Frans Thamura <frans at meruvian.org> wrote:
>>
>>>>
>>>> I guess the "it´s not open enough" doomsday preaching and complaining can
>>>> begin now...
>>>> *sarcasm*
>>>>
>>> hehe
>>>
>>> it is not standard also :(
>>>
>>> I think OpenJDK move to standard based on JCP,
>>>
>>> with JFX will break the JDK mindset, and this mean , close
>>> implementation to any JVM spec, like Android did..
>>>
>>> F
>>
More information about the discuss
mailing list