Does Java 8 delay mean less app developer feedback?
richard.bair at oracle.com
Thu May 2 08:56:41 PDT 2013
I don't think Danno was making light of it at all, but rather was looking at "how can we solve this problem without waiting for Oracle"? which is pretty dang reasonable IMO.
1) Once OpenJFX is fully opensourced, could the v8 targeted branch be compiled to run on JDK 7?
So this question is basically asking, when OpenJFX is fully open, can it be built and targeted at 7? In other words, maybe for your produce you could use OpenJDK and OpenJFX instead of Oracle's provided JavaFX 2.x? If this worked, then you could use the latest FX with an older JRE.
2) Or key stoppers fixed in a separate community maintained branch?
If there is some reason #1 won't work (for example, we're about to get tied to Java 8 language features with the fix for filtered / sorted observable lists), can a "back port" of JavaFX 8 for running against 7 be maintained by the community?
3) Perhaps v8.1 should be the one to go lambda crazy?
In order to reduce the pain of #2, maybe we shouldn't go crazy adding a bunch of lambdas into JavaFX 8?
Danno was totally being productive here trying to help solve your problem!
On May 2, 2013, at 8:40 AM, Randahl Fink Isaksen <randahl at rockit.dk> wrote:
> Danno, I take offence to that. Your comments does in no way represent what I am asking. If you looked into Jira you would see that a lot of issues do in no way require Java 8 or JavaFX 8, but still they are scheduled to be released along with FX8. What I am asking is for some of the minor issues to be rescheduled because of Oracle's recently announced delay.
> One example is the Jira issue that requests source code to be provided along with JavaFX. This is a requirement for NetBeans code completion to work. It is now scheduled for FX8. Is Java 8 or FX 8 a requirement before this issue can be solved? No. Would it be nice not having to wait a full year to have the source code distributed along with JavaFX? Yes.
> If you are here to mock a serious request, I wonder if the community thinks you are welcome.
> On May 2, 2013, at 17:25 , Danno Ferrin <danno.ferrin at shemnon.com> wrote:
>> Once OpenJFX is fully opensourced, could the v8 targeted branch be compiled to run on JDK 7?
>> Or key stoppers fixed in a separate community maintained branch?
>> Perhaps v8.1 should be the one to go lambda crazy?
>> On Thu, May 2, 2013 at 1:11 AM, Randahl Fink Isaksen <randahl at rockit.dk> wrote:
>> Oracle has delayed Java 8 until Q1 of 2014, which means FX 8 is delayed likewise, I suppose.
>> Now, I have identified and filed quite a lot of JavaFX issues, but more and more of them are being targeted for FX8. I would like to provide feedback as the issues are resolved, but I can no longer do that since – like everyone else – I am developing an app using the current JavaFX release. I cannot help but wonder how many other app developers are now providing less feedback, and I fear that this will have a considerable negative impact on the quality of JavaFX. If no feedback is provided on many of the resolved issues until they are finally released all at once in Q1 2014, there is guaranteed to be QA problems – big bang is rarely a viable development strategy.
>> I would like to ask if this has been discussed, and if the JavaFX development team has considered moving issues from FX8 back to the ordinary incremental 2.2.x releases to strengthen the collaboration between app developers and API developers.
>> There is nothing that will hold me back. I know who I am....
>> I remember wher I came from, and I feel stronger for knowing.
>> Zane, Ninja of Ice. Ninjago S01E07
More information about the openjfx-dev