<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Hi, <br>
thanks for your time, I appreciate the answer.<br>
<br>
I love JavaFX and my concern is sincere.<br>
JavaFX is not a "complete solution" to build UIs because it relies
on AWT for basic and important features like a TrayIcon for example.<br>
<br>
AWT is abandoned, most of its APIs is falling apart causing issues
on modern OS.<br>
<br>
That's why of my question. If AWT is abandoned, how can JavaFX
survive this?<br>
Does it has sense in developing JavaFX if Oracle abandoned AWT?<br>
<br>
I know that JavaFX devs thinks that AWT and JavaFX are two separate
things but for devs that must develop a software that has a UI, <br>
JavaFX is not enough because JavaFX has "nearly no integration with
the OS".<br>
<br>
I mean, how can we convince new developers to jump on JavaFX if the
"surroundings" are in this state?<br>
<br>
Davide<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 28/09/2024 20:37, Johan Vos wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CABxFH2FybU_nnPifH+nbOMASMq4G-Zx9VmQ2F1cXOw9SfaVCxw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">I got the question "Will JavaFX survive?" very
often since I became co-lead of the OpenJFX project, about 7
years ago. OpenJFX is a technology project and contrary to most
client frameworks OpenJFX itself has no marketing department
with "devrels" etc.
<div>The resources working on OpenJFX are focusing on the
technology. And I am very proud to see that the code you could
write for JavaFX 9 is still running today on JavaFX 23. I
don't think many client technologies can say the same. </div>
<div>The diverse contributors to the OpenJFX project are doing a
fantastic job in maintaining and advancing the technology in
the spirit of OpenJDK and Java in general. Granted, I
sometimes wish we (as in OpenJFX) had some marketing efforts
of paid devrels to spread the word at many conferences. But as
developers, our first priority and main skills are in working
on the code.</div>
<div><br>
</div>
<div>- Johan</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat, Sep 28, 2024 at
5:17 PM Davide Perini <<a
href="mailto:perini.davide@dpsoftware.org"
moz-do-not-send="true" class="moz-txt-link-freetext">perini.davide@dpsoftware.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">no
answers, means a lot...<br>
<br>
On 26/09/2024 17:44, Davide Perini wrote:<br>
> As title.<br>
> AWT is too old to withstand the future and probably it's
too old to <br>
> withstand the present.<br>
><br>
> AWT is falling apart with old APIs breaking as operating
systems move on.<br>
><br>
> Even very important features like tray icons and
notifications are <br>
> broken.<br>
> Something is broken in Windows, something in Linux,
something on macOS.<br>
><br>
> Current notification APIs is old and is somewhat broken
in Windows <br>
> with notification that doesn't stick in the notification
center.<br>
><br>
> SystemTray on Linux is completely broken because it still
uses the <br>
> ancient xembeds instead of the newer SNI.<br>
><br>
> I love JavaFX but will JavaFX survive the fact that AWS
is abandoned <br>
> and that it is falling apart?<br>
><br>
> Is there something moving to renew AWT or it's just
kicking a dead horse?<br>
><br>
> Thanks<br>
> Davide<br>
<br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>