<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
These are all good points. One thing we can do is make sure that
there are open JBS Enhancement issues tracking the features that are
being asked for. Prioritizing them, and eventually implementing some
of them, will be a discussion for a different day. As Johan said, we
don't want to over-commit.<br>
<br>
-- Kevin<br>
<br>
<br>
<div class="moz-cite-prefix">On 11/27/2023 10:49 AM, Johan Vos
wrote:<br>
</div>
<blockquote type="cite" cite="mid:CABxFH2EZ-kjnhL95SOTG8exkMV69ajb1yw1JDi69aUm2QfnMdA@mail.gmail.com">
<div dir="ltr">I've read the responses to this post, and I think
they all make sense, so this is great feedback. It's good to
know what people are missing/interested in.
<div><br>
<div>However, it makes me a bit nervous to see a growing
wishlist while I don't see more funding. Unfortunately, the
reality is that most companies want to pay (lots of money)
for JavaFX consulting but not for the core development. </div>
<div>Other client frameworks typically "solve" this by
indirect revenue streams (tie a client to a backend
technology or ad-driven revenue system), or by lowering the
quality bar. I really want to avoid the latter (and also the
ad-driven revenue stream). While it would not be too hard to
come up with new features that address most of the requests,
I believe we need to make sure that</div>
<div>1. what we deliver is top-quality</div>
<div>2. what we delivered can be maintained for the next 10
years.</div>
<div><br>
</div>
<div>Quality and backward compatibility are extremely
important to the success of most Java projects. I am aware
that the OpenJFX review process is sometimes a bottleneck to
get new features in, but it is really something that we have
to take very seriously.</div>
<div><br>
</div>
<div>I don't want to start the business discussion here, as
this is a tech-only list. But I want to be careful with
over-promising, as the past years taught me that maintaining
the core of JavaFX on a number of supported platforms is
already a very challenging task. I am very excited to see
our achievements, having 2 major releases every year and
many updates, with different LTS versions being supported,
delivering SDK's, jmods, maven artifacts.</div>
<div><br>
</div>
<div>The work on the core-platform is typically not something
that makes the christmas wish-lists, but keep it in mind
during the dark days :)</div>
<div><br>
</div>
<div>Having said that: on my wishlist is a Headless Glass
platform. I'll write more about that later in a separate
post.</div>
<div><br>
</div>
<div>- Johan</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Nov 15, 2023 at
9:49 AM Dirk Lemmermann <<a href="mailto:dlemmermann@gmail.com" moz-do-not-send="true" class="moz-txt-link-freetext">dlemmermann@gmail.com</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">Hi
guys,<br>
<br>
I already mentioned this at the JavaFX BOF at DEVOXX and also
posted this on Twitter but wanna make sure it gets the
visibility it deserves:<br>
<br>
All I want for Christmas is … / what I think is needed for
JavaFX going forward ...<br>
<br>
- removal of AWT <br>
- a tray API (tray icon) <br>
- undecorated interactive stage style <br>
- blur support for stages <br>
- WebP image format support <br>
- native embedded browser (Chromium) <br>
- 3D line and point primitives <br>
- injection support in FXML for custom controls <br>
- TableView improvements, aka. TableView2<br>
<br>
(order of items does not imply priority)<br>
<br>
Dirk<br>
<br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>