Re: javadoc changes [was: openjfx-dev Digest, Vol 73, Issue 25]

2017-12-16 Thread Nir Lisker
Sorry about the subject line, I believe the gmail web client is not very suitable for mailing lists. If anyone has suggestions about it please let me know (privately or publicly). The schedule is fine for me, 2-3 weeks should be more than enough. I have 2 sets of changes in mind. One is

Re: javadoc changes [was: openjfx-dev Digest, Vol 73, Issue 25]

2017-12-15 Thread Kevin Rushforth
[fixed subject line] The freeze for the last planned integration prior to RDP2 will be on 1/15/2018 (end of the day Pacific time), so this is the deadline. RDP2 starts on 1/18/2018. See the jdk10 project page [1] for all JDK 10 dates. I hope to fix at least a first pass of the build

Re: openjfx-dev Digest, Vol 73, Issue 25

2017-12-15 Thread Nir Lisker
find at the end > >>>> that Oracle either doesn?t like the design, implementation or > something > >>>> else then it is wasted time I?ll never get back. > >>>>>>>> There are lots of other innovations too that I would like to > >>>>>>>> see in > >>>> JavaFX but I just don?t ?feel the enthusiasm? from Oracle. > >>>> > >>>>>>>> If there is someone on the JavaFX team who would be willing to > >>>>>>>> work > >>>> with me (at least in some capacity), please have them contact me > >>>> privately via email. > >>>>>>>> The innovations I could work on and contribute include: > >>>>>>>> > >>>>>>>> > >>>>>>>> 1. WebGL support in WebView > >>>>>>>> 2. Better text support including text documents& rich text > >>>>>>>> editors > >>>> etc. > >>>>>>>> 3. Significant improvements in scene graph rendering speed > >>>>>>>> using > >>>> modern game-engine style structures and algorithms > >>>>>>>> JavaFX cannot survive without innovation and I am keen to see > >>>>>>>> it > >>>> happen and contribute as much as possible. > >>>>>>>> Graciously, > >>>>>>>> > >>>>>>>> > >>>>>>>> John-Val Rose > >>>>>>>> Rosethorn Technology > >>>>>>>> > >>>>>>>> > >>>>>>>>> On 6 Dec 2017, at 11:36, jav...@use.startmail.com wrote: > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> Sorry about all the typos previously. > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> Question- why not use the code in awt ? I am not totally up > >>>>>>>>> on > >>>> what's going on with the platforms' native rendering engines ( > meaning, > >>>> I > >>>> have no idea whatsoever) or how they have changed, but golly it sure > >>>> does still work pretty well. > >>>>>>>>> At least it seems to me looking at awt that a smallish number > >>>>>>>>> of > >>>> things are 1) well defined by the native platofrm and 2) would more or > >>>> less translate directly to an Java API and 3) from those small number > of > >>>> building blocks, (Font and Glyph metrics and this kind of thing) > >>>> text line layout algorithms can be written by ordinary civilians along > >>>> with all the other stuff that goes into a text editor. > >>>>>>>>> And yes, everything does look easy when someone else is going > >>>>>>>>> to do > >>>> it. > >>>>>>>>> > >> > >> > > > > -- > > Message: 2 > Date: Fri, 15 Dec 2017 15:22:46 + (UTC) > From: Tamer KARAKAN <tamerkara...@yahoo.com> > To: "openjfx-dev@openjdk.java.net" <openjfx-dev@openjdk.java.net> > Message-ID: <36404373.276859.1513351366...@mail.yahoo.com> > Content-Type: text/plain; charset=UTF-8 > > > > Android?de Yahoo Postadan g?nderildi > > -- > > Message: 3 > Date: Sat, 16 Dec 2017 02:58:50 +1100 > From: John-Val Rose <johnvalr...@gmail.com> > To: "openjfx-dev@openjdk.java.net" <openjfx-dev@openjdk.java.net> > Subject: Re: Innovation ?essay? > Message-ID: <1d17c354-fcb8-4af6-b491-9f6d97a39...@gmail.com> > Content-Type: text/plain; charset=utf-8 > > It?s been noted that my previous email was very much in the ?TL;DR? > category. > > I?m sorry about that. > > I guess I just had a lot to say and feel very passionate about JavaFX. > > Graciously, > > John-Val Rose > > -- > > Message: 4 > Date: Fri, 15 Dec 2017 10:55:56 -0800 > From: Kevin Rushforth <kevin.rushfo...@oracle.com> > To: "openjfx-dev@openjdk.java.net" <openjfx-dev@openjdk.java.net> > Subject: PLEASE READ: JDK10 RDP1 process for JavaFX > Message-ID: <5a341abc.70...@oracle.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > To: OpenJFX Committers > > As you should have seen from the message I forwarded from Mark Reinhold, > the JDK 10 RDP1 (proposed) rules have been posted. > > During RDP1 there is no additional approval needed, beyond the usual > code review, to push the following types of fixes: > > * P1-P3 bugs [1] > > * P1-P5 test and javadoc bugs (must have noreg-self or noreg-doc label) > > Note that RFEs are no longer allowed in JDK 10 [2] > > Most fixes will go into jfx-dev/rt for 11, but for those fixes that meet > the above criteria, they can go directly in 10-dev/rt. As such, > openjfx/10-dev/rt has been reopened for FX fixes for JDK 10. Please ask > if you have any questions. > > If you want to get a bug fix into JDK 10, it is your responsibility to > push it there. I will sync from 10-dev --> jfx-dev periodically (roughly > once a week, but possibly more often). Alternatively, you can push it to > both places if you want the fix into jfx-dev sooner (or you can push to > jfx-dev first and then later backport it to 10-dev). > > -- Kevin > > [1] Especially for P3 bugs, make sure it is a safe fix and that the > priority is correct, and not "I want to get this in so I'll call it a P3" > > [2] Without prior approval from the JDK project lead, and such approval > is not expected to be given > > > > End of openjfx-dev Digest, Vol 73, Issue 25 > *** >