Re: [jfx16] RFR: 8252389: Fix mistakes in FX API docs [v3]

2021-02-02 Thread Ajit Ghaisas
On Sat, 30 Jan 2021 20:21:59 GMT, Nir Lisker wrote: >> The usual doc fixes (for OpenJFX 16). >> >> Can wait until RDP2 to see if something else comes up. > > Nir Lisker has updated the pull request incrementally with one additional > commit since the last revision: > > Addressed review

Re: Make javafx.controls open and community-driven

2021-02-02 Thread Julian Jupiter
Desktop is already a smaller market compared before. And the competition has become toucher because of several toolkits out there - Electron, Flutter, Compose for Desktop, etc. Hence, the need for more open and community-driven JavaFX project. On Wed, Feb 3, 2021, 12:14 PM Ty Young, wrote: > On

Re: Make javafx.controls open and community-driven

2021-02-02 Thread Ty Young
On 2/2/21 8:16 PM, Nir Lisker wrote: Hi Mike, First of all, I would have you consider revisiting your medical observation on the state of JavaFX. If you've read the almost-weekly recurrent threads of "should I use Swing or JavaFX" in r/Java, you'd realize that reports of JavaFX's death are

Re: RFR: 8260475: Deprecate for removal protected access members in DateTimeStringConverter [v2]

2021-02-02 Thread Nir Lisker
> Deprecating protected members in DateTimeStringConverter. Internal > implementation should not be exposed (similar to `NumberStringConverter` and > others). Nir Lisker has updated the pull request incrementally with one additional commit since the last revision: Added javadoc deprecation

Re: Make javafx.controls open and community-driven

2021-02-02 Thread Nir Lisker
Hi Mike, First of all, I would have you consider revisiting your medical observation on the state of JavaFX. If you've read the almost-weekly recurrent threads of "should I use Swing or JavaFX" in r/Java, you'd realize that reports of JavaFX's death are greatly exaggerated. But yes, it is very

Re: Make javafx.controls open and community-driven

2021-02-02 Thread Kevin Rushforth
There are two separate issues here. I won't address the first point from the initial poster, other than to say that I understand that the lack of direct write access to JBS for occasional contributors is a pain point. I don't think it is stopping anyone from contributing, though. As for the

Re: Make javafx.controls open and community-driven

2021-02-02 Thread Michael Paus
1+ Am 02.02.21 um 15:12 schrieb Pedro Duque Vieira: Hi, Although I don't agree with everything said here at the start of this thread, I agree with the base idea that JavaFX would benefit from being more open than it is currently. It's something I've already said here in this mailing list and

Re: Make javafx.controls open and community-driven

2021-02-02 Thread Pedro Duque Vieira
Hi, Although I don't agree with everything said here at the start of this thread, I agree with the base idea that JavaFX would benefit from being more open than it is currently. It's something I've already said here in this mailing list and since it's been a while and that discussion probably

Re: RFR: 8255572: Axis does not compute preferred height properly when autoRanging is off [v3]

2021-02-02 Thread Jeanette Winzenburg
On Tue, 22 Dec 2020 09:32:36 GMT, Ajit Ghaisas wrote: > > > At first, I thought this setTickLabelRotation() call violates the method > javadoc above. On a second look, I found that the javadoc is applicable only > if AutoRanging() is true. > Method calls - calculateNewSpacing() and

Re: RFR: 8255572: Axis does not compute preferred height properly when autoRanging is off [v6]

2021-02-02 Thread Jeanette Winzenburg
On Mon, 1 Feb 2021 23:13:02 GMT, Jonathan Vusich wrote: >> I do see that there are no changes from last time, which is good, so it will >> be fine for this time. >> >> When ready, you can add the new test by pushing a new commit. > > @kevinrushforth I was not aware of that, thank you for