I assume since JFX stated with and was closely coupled with Java prior to being
removed from the JDK/JRE, this allow for the link up with the java bug link.
The case could be made it could be similar to the other library’s. I believe
some other existing libraries (JAXB?) were removed [maybe
I think I can comment from the perspective of a successful user of JavaFX
(we have been running an administration application for our medical
software for over 5 years now) as well as a part-time contributor to the
JavaFX project (with the help of Kevin Rushforth and Ajit Ghaisas my pull
request
What do you think about decoupling javafx.controls from other modules private
API? Is it possible? In current situation
it may be the best solution, because this would allow to fork it. So, those who
interested could play with fork(s) and
backport changes when neccessary. It would also allow to
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
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
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
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
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
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
I have to agree. All the protection measures, although well intended
originally, are not helping.
On 2-2-2021 08:02, Julian Jupiter wrote:
Yes, please!
Julez
On Tue, Feb 2, 2021, 2:37 PM , wrote:
Hello.
JavaFX is a great toolkit, which personally I like a lot, but it's slowly
dying
Yes, please!
Julez
On Tue, Feb 2, 2021, 2:37 PM , wrote:
> Hello.
>
> JavaFX is a great toolkit, which personally I like a lot, but it's slowly
> dying for the past 5 years. You can barely
> argue with that. Most of the devs still prefer Swing. Have a look how many
> topics like "JavaFX is
Hello.
JavaFX is a great toolkit, which personally I like a lot, but it's slowly dying
for the past 5 years. You can barely
argue with that. Most of the devs still prefer Swing. Have a look how many
topics like "JavaFX is dead" on Reddit or
similar resources. Look how many community libraries
12 matches
Mail list logo
