Re: My JavaFX Christmas Wishlist

[Kevin Rushforth]

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.


-- Kevin


On 11/27/2023 10:49 AM, Johan Vos wrote:
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.


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.
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

1. what we deliver is top-quality
2. what we delivered can be maintained for the next 10 years.

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.


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.


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 :)


Having said that: on my wishlist is a Headless Glass platform. I'll 
write more about that later in a separate post.


- Johan





On Wed, Nov 15, 2023 at 9:49 AM Dirk Lemmermann 
 wrote:


Hi guys,

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:

All I want for Christmas is … / what I think is needed for JavaFX
going forward ...

        - removal of AWT
        - a tray API (tray icon)
        - undecorated interactive stage style
        - blur support for stages
        - WebP image format support
        - native embedded browser (Chromium)
        - 3D line and point primitives
        - injection support in FXML for custom controls
        - TableView improvements, aka. TableView2

(order of items does not imply priority)

Dirk

Re: My JavaFX Christmas Wishlist

[Johan Vos]

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.

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.
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
1. what we deliver is top-quality
2. what we delivered can be maintained for the next 10 years.

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.

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.

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 :)

Having said that: on my wishlist is a Headless Glass platform. I'll write
more about that later in a separate post.

- Johan





On Wed, Nov 15, 2023 at 9:49 AM Dirk Lemmermann 
wrote:

> Hi guys,
>
> 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:
>
> All I want for Christmas is … / what I think is needed for JavaFX going
> forward ...
>
> - removal of AWT
> - a tray API (tray icon)
> - undecorated interactive stage style
> - blur support for stages
> - WebP image format support
> - native embedded browser (Chromium)
> - 3D line and point primitives
> - injection support in FXML for custom controls
> - TableView improvements, aka. TableView2
>
> (order of items does not imply priority)
>
> Dirk
>
>

RE: My JavaFX Christmas Wishlist

[Pedro Duque Vieira]

In the spirit of Christmas and of this thread here is my wish list 😊



1 - The number one thing I’d change would be to make JavaFX “more
extendable”. By this I mean having more hooks to extend core areas of
JavaFX (CSS parser, 3D, etc).

The reason I ask for this is because it’s much easier for an outsider to
add functionality to JavaFX by developing his own library that interfaces
with the javafx platform than it is to actually contribute code to the core
platform itself.  For a number of reasons, like: the goals of the
contributor might not align with the people managing the platform, it’s
much more work and has a much stepper learning curve to contribute code to
the platform, the core platform needs to maintain backwards compatibility,
etc..

I believe this could make JavaFX evolve faster and more.

Imagine if a JavaFX library developer could extend everything about the
JavaFX CSS engine to add functionality like layout, animations, etc, etc
(all the bells and whistles you now see in web css). Or imagine if you
could more easily extend 3D with new 3D primitives, etc..

2 – Add the possibility of specifying more than 1 stylesheet as the user
agent stylesheet (also possible with the new StyleTheme API proposal).
There’s a missing piece when it comes to allowing developers to create
custom themes: you can’t specify more than 1 stylesheet to be the user
agent stylesheet. This would be a rather easy change that I think could
provide a big value.

3 – Pixel shaders. The most stunning things in the UI space nowadays are
being created by leveraging pixel shaders. This is something that for
instance Jetpack Compose (and Skia) provides and other UI frameworks have
as well.

4 – Improve font rendering (seems to affect Windows more than Mac)

5 – Background blur

6 – JavaFX Skin having a better separation between view and controller
part. Right now you have the model (the class extending from JavaFX
Control) but you don’t have a clear View. In all javafx sdk controls both
Controller and View are present in the same Skin class.

7 – New TableView



Thanks! And Merry Christmas to everyone (although it's still more than 1
month till Christmas 😊)

-- 
Pedro Duque Vieira - https://www.pixelduke.com


Sem
vírus.www.avg.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

RE: My JavaFX Christmas Wishlist

[Jan Tosovsky]

On 2023-11-15, Dirk Lemmermann wrote:
> 
> All I want for Christmas is … / what I think is needed for JavaFX 
> going forward ...

I wish JavaFX better MARKETING. If I sometimes encounter articles comparing 
various frameworks for building desktop apps, JavaFX is never listed. 

I was sad about it, but nowadays, seeing the rapid progress of novel frameworks 
like Tauri or Flutter, I tend to understand JavaFX is becoming obsolete. Java 
itself has a bad reputation in the young generation.

I am losing hope JavaFX can compete, be sexy again, attract people, volunteers 
willing to implement missing features...

I would be grateful to be wrong. JavaFX still has my sympathy. It won my 
desktop app frameworks comparison [1] but it itself can hardly revert the 
trend. 

So, in sum, I wish JavaFX better MARKETING, so it was more visible than today. 
From my POV it is the key to change the status quo.

Jan

___
[1] 
https://medium.com/@jan.tosovsky.cz/comparing-modern-multiplatform-desktop-frameworks-on-the-image-browser-app-305552c7ebe2

Re: My JavaFX Christmas Wishlist

[Scott Palmer]

> On Nov 15, 2023, at 9:32 AM, Nir Lisker  wrote:
> 
> 
>> removal of AWT
> 
> Isn't that *a lot* of work? All the image IO is AWT, no? 

It was a mistake to tie ImageIO to GUI framework image classes. The image 
raster should be returned in a generic wrapper around a byte array or 
ByteBuffer from the various codecs. 
The UI layer should bridge it from there. A WriteableRaster or BufferImage just 
needs to wrap those bytes with the dimensions and pixel format details.
But I bet it isn’t that far off and wouldn’t be that much work. It’s a question 
of priorities though. 

I still think the AWT ties need to be cut.

I want native tray support, dock icon overlays/badges & progress feedback. 
Webcam support would be nice too, for video chat apps, security camera UIs, 
image recognition, barcode scanning, etc. 

Scott

Re: My JavaFX Christmas Wishlist

[Kevin Rushforth]

There are some interesting things on this list, and in some of the 
follow-on messages. This reply is just looking at the AWT issue.


It depends on what you mean by "remove AWT". Removing all internal 
dependencies (aside from Swing/JavaFX interop of course) on java.desktop 
(AWT/Swing/Java2D) and providing replacement API for the functionality 
that is missing in JavaFX would be a very large effort. At a minimum:


Implementation dependencies:
* Refactor Java Beans implementation in javafx.base such that 
java.desktop is optional
* Rewrite implementation of JavaFX printing to use native printing 
capability (this is a large effort)
* Any other places where the implementation in javafx.graphics uses some 
Java2D utilities (it looks like we might have removed the last of these)


New API for missing features to reach parity with java.desktop:
* Image I/O (this is the largest piece)
* Image operators
* Headless support
* Desktop integration (we want to do this anyway at some point)

If all you need from the list of missing features w.r.t. java.desktop is 
a Tray Icon (part of desktop integration), the largest piece would be 
the printing dependency. If you don't print, and can do a custom build 
of JavaFX to remove it, it might not be too bad, but still work.


-- Kevin


On 11/16/2023 1:08 AM, Dirk Lemmermann wrote:
It is mainly an issue when trying to run a JavaFX app natively 
(GraalVM, Gluon). You can not have AWT in your classpath when 
compiling to native code. It is not supported.

Dirk

Am 15.11.2023 um 20:31 schrieb David Alayachew 
:


My bigger question is asking what you lose by having AWT in JavaFX. 
Is there something fundamentally problematic about it that its 
removal would solve/alleviate a problem?


Whereas on the other hand, AWT has some very useful libraries that 
are in use by nearly all Java GUI frameworks. For example, if you 
want to do anything really complex with 2D Image work, you will 
inevitably end up using java.awt.BufferedImage. It's simple, but very 
fast.


On Wed, Nov 15, 2023 at 12:18 PM Dirk Lemmermann 
 wrote:


3D: unfortunately that is completely out of my comfort zone … for
this feature request I am merely the messenger.
AWT: I was thinking that this is mostly a refactoring and
probably code duplication?

Dirk


Am 15.11.2023 um 14:28 schrieb Nir Lisker :

3D line and point primitives


I filed https://bugs.openjdk.org/browse/JDK-8316398 for this
already. As noted, it requires a somewhat complex computation
for intersections and possibly for contains. If you would like
to write these Mesh classes, like the current TriangleMesh, I
can write the rest.

removal of AWT


Isn't that *a lot* of work? All the image IO is AWT, no?

On Wed, Nov 15, 2023 at 10:48 AM Dirk Lemmermann
 wrote:

Hi guys,

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:

All I want for Christmas is … / what I think is needed for
JavaFX going forward ...

        - removal of AWT
        - a tray API (tray icon)
        - undecorated interactive stage style
        - blur support for stages
        - WebP image format support
        - native embedded browser (Chromium)
        - 3D line and point primitives
        - injection support in FXML for custom controls
        - TableView improvements, aka. TableView2

(order of items does not imply priority)

Dirk

Re: My JavaFX Christmas Wishlist

[Dirk Lemmermann]

It is mainly an issue when trying to run a JavaFX app natively (GraalVM, 
Gluon). You can not have AWT in your classpath when compiling to native code. 
It is not supported.
 
Dirk

> Am 15.11.2023 um 20:31 schrieb David Alayachew :
> 
> My bigger question is asking what you lose by having AWT in JavaFX. Is there 
> something fundamentally problematic about it that its removal would 
> solve/alleviate a problem?
> 
> Whereas on the other hand, AWT has some very useful libraries that are in use 
> by nearly all Java GUI frameworks. For example, if you want to do anything 
> really complex with 2D Image work, you will inevitably end up using 
> java.awt.BufferedImage. It's simple, but very fast.
> 
> On Wed, Nov 15, 2023 at 12:18 PM Dirk Lemmermann  > wrote:
>> 3D: unfortunately that is completely out of my comfort zone … for this 
>> feature request I am merely the messenger.
>> AWT: I was thinking that this is mostly a refactoring and probably code 
>> duplication?
>> 
>> Dirk
>> 
>>> Am 15.11.2023 um 14:28 schrieb Nir Lisker >> >:
>>> 
 3D line and point primitives
>>> 
>>> I filed https://bugs.openjdk.org/browse/JDK-8316398 for this already. As 
>>> noted, it requires a somewhat complex computation for intersections and 
>>> possibly for contains. If you would like to write these Mesh classes, like 
>>> the current TriangleMesh, I can write the rest.
>>> 
 removal of AWT
>>> 
>>> Isn't that *a lot* of work? All the image IO is AWT, no? 
>>> 
>>> On Wed, Nov 15, 2023 at 10:48 AM Dirk Lemmermann >> > wrote:
 Hi guys,
 
 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:
 
 All I want for Christmas is … / what I think is needed for JavaFX going 
 forward ...
 
 - removal of AWT 
 - a tray API (tray icon) 
 - undecorated interactive stage style 
 - blur support for stages 
 - WebP image format support 
 - native embedded browser (Chromium) 
 - 3D line and point primitives 
 - injection support in FXML for custom controls 
 - TableView improvements, aka. TableView2
 
 (order of items does not imply priority)
 
 Dirk
 
>> 

Re: My JavaFX Christmas Wishlist

[Andy Goryachev]

In the spirit of the season, here is my wish list (in no particular order):

- bundling javafx with jdk by default
- playback/display of all the modern A/V/I formats (webp, heic, svg, ...)
- application framework: settings, ui preferences, actions, programmatic css, 
platform api
- cross-platform jpackage, at least for win/linux/macos
- improvements to the core platform: better focus management, actions, text 
enhancements, ...

:-)

-andy




From: openjfx-dev  on behalf of David Alayachew 

Date: Wednesday, November 15, 2023 at 11:31
To: Dirk Lemmermann 
Cc: Nir Lisker , openjfx-dev 
Subject: Re: My JavaFX Christmas Wishlist
My bigger question is asking what you lose by having AWT in JavaFX. Is there 
something fundamentally problematic about it that its removal would 
solve/alleviate a problem?

Whereas on the other hand, AWT has some very useful libraries that are in use 
by nearly all Java GUI frameworks. For example, if you want to do anything 
really complex with 2D Image work, you will inevitably end up using 
java.awt.BufferedImage. It's simple, but very fast.

On Wed, Nov 15, 2023 at 12:18 PM Dirk Lemmermann 
mailto:dlemmerm...@gmail.com>> wrote:
3D: unfortunately that is completely out of my comfort zone … for this feature 
request I am merely the messenger.
AWT: I was thinking that this is mostly a refactoring and probably code 
duplication?

Dirk


Am 15.11.2023 um 14:28 schrieb Nir Lisker 
mailto:nlis...@gmail.com>>:

3D line and point primitives

I filed https://bugs.openjdk.org/browse/JDK-8316398 for this already. As noted, 
it requires a somewhat complex computation for intersections and possibly for 
contains. If you would like to write these Mesh classes, like the current 
TriangleMesh, I can write the rest.

removal of AWT

Isn't that *a lot* of work? All the image IO is AWT, no?

On Wed, Nov 15, 2023 at 10:48 AM Dirk Lemmermann 
mailto:dlemmerm...@gmail.com>> wrote:
Hi guys,

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:

All I want for Christmas is … / what I think is needed for JavaFX going forward 
...

- removal of AWT
- a tray API (tray icon)
- undecorated interactive stage style
- blur support for stages
- WebP image format support
- native embedded browser (Chromium)
- 3D line and point primitives
- injection support in FXML for custom controls
- TableView improvements, aka. TableView2

(order of items does not imply priority)

Dirk

Re: My JavaFX Christmas Wishlist

[Chad Preisler]

I agree with Wayland. It is inevitable, and I want JavaFX to perform well
on Linux.

On Wed, Nov 15, 2023 at 2:16 PM Thiago Milczarek Sayão <
thiago.sa...@gmail.com> wrote:

> Hi,
>
> I would choose:
>
> - Wayland
> - Vulkan rendering
> - Copyable labels
> - A pay raise for Kevin :)
>
>
>
>
>
>
>
>
> Em qua., 15 de nov. de 2023 07:25, Dirk Lemmermann 
> escreveu:
>
>> Hi guys,
>>
>> 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:
>>
>> All I want for Christmas is … / what I think is needed for JavaFX going
>> forward ...
>>
>> - removal of AWT
>> - a tray API (tray icon)
>> - undecorated interactive stage style
>> - blur support for stages
>> - WebP image format support
>> - native embedded browser (Chromium)
>> - 3D line and point primitives
>> - injection support in FXML for custom controls
>> - TableView improvements, aka. TableView2
>>
>> (order of items does not imply priority)
>>
>> Dirk
>>
>>

Re: My JavaFX Christmas Wishlist

[Michael Strauß]

- more reviewers to tackle the perpetual review bottleneck

Re: My JavaFX Christmas Wishlist

[David Alayachew]

My bigger question is asking what you lose by having AWT in JavaFX. Is
there something fundamentally problematic about it that its removal would
solve/alleviate a problem?

Whereas on the other hand, AWT has some very useful libraries that are in
use by nearly all Java GUI frameworks. For example, if you want to do
anything really complex with 2D Image work, you will inevitably end up
using java.awt.BufferedImage. It's simple, but very fast.

On Wed, Nov 15, 2023 at 12:18 PM Dirk Lemmermann 
wrote:

> 3D: unfortunately that is completely out of my comfort zone … for this
> feature request I am merely the messenger.
> AWT: I was thinking that this is mostly a refactoring and probably code
> duplication?
>
> Dirk
>
> Am 15.11.2023 um 14:28 schrieb Nir Lisker :
>
> 3D line and point primitives
>>
>
> I filed https://bugs.openjdk.org/browse/JDK-8316398 for this already. As
> noted, it requires a somewhat complex computation for intersections and
> possibly for contains. If you would like to write these Mesh classes, like
> the current TriangleMesh, I can write the rest.
>
> removal of AWT
>>
>
> Isn't that *a lot* of work? All the image IO is AWT, no?
>
> On Wed, Nov 15, 2023 at 10:48 AM Dirk Lemmermann 
> wrote:
>
>> Hi guys,
>>
>> 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:
>>
>> All I want for Christmas is … / what I think is needed for JavaFX going
>> forward ...
>>
>> - removal of AWT
>> - a tray API (tray icon)
>> - undecorated interactive stage style
>> - blur support for stages
>> - WebP image format support
>> - native embedded browser (Chromium)
>> - 3D line and point primitives
>> - injection support in FXML for custom controls
>> - TableView improvements, aka. TableView2
>>
>> (order of items does not imply priority)
>>
>> Dirk
>>
>>
>

Re: My JavaFX Christmas Wishlist

[Mark Raynsford]

On Wed, 2023-11-15 at 15:37 -0300, Thiago Milczarek Sayão wrote:
> - Vulkan rendering

Seconded!

> - A pay raise for Kevin :)

Seconded!


-- 
Mark Raynsford | https://www.io7m.com

Re: My JavaFX Christmas Wishlist

[Andy Goryachev]

+1 for pay raise for Kevin

:-)


-andy

From: openjfx-dev  on behalf of Thiago Milczarek 
Sayão 
Date: Wednesday, November 15, 2023 at 10:38
To: Dirk Lemmermann 
Cc: openjfx-dev 
Subject: Re: My JavaFX Christmas Wishlist
Hi,

I would choose:

- Wayland
- Vulkan rendering
- Copyable labels
- A pay raise for Kevin :)








Em qua., 15 de nov. de 2023 07:25, Dirk Lemmermann 
mailto:dlemmerm...@gmail.com>> escreveu:
Hi guys,

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:

All I want for Christmas is … / what I think is needed for JavaFX going forward 
...

- removal of AWT
- a tray API (tray icon)
- undecorated interactive stage style
- blur support for stages
- WebP image format support
- native embedded browser (Chromium)
- 3D line and point primitives
- injection support in FXML for custom controls
- TableView improvements, aka. TableView2

(order of items does not imply priority)

Dirk

Re: My JavaFX Christmas Wishlist

[Thiago Milczarek Sayão]

Hi,

I would choose:

- Wayland
- Vulkan rendering
- Copyable labels
- A pay raise for Kevin :)








Em qua., 15 de nov. de 2023 07:25, Dirk Lemmermann 
escreveu:

> Hi guys,
>
> 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:
>
> All I want for Christmas is … / what I think is needed for JavaFX going
> forward ...
>
> - removal of AWT
> - a tray API (tray icon)
> - undecorated interactive stage style
> - blur support for stages
> - WebP image format support
> - native embedded browser (Chromium)
> - 3D line and point primitives
> - injection support in FXML for custom controls
> - TableView improvements, aka. TableView2
>
> (order of items does not imply priority)
>
> Dirk
>
>

Re: My JavaFX Christmas Wishlist

[Dirk Lemmermann]

3D: unfortunately that is completely out of my comfort zone … for this feature 
request I am merely the messenger.
AWT: I was thinking that this is mostly a refactoring and probably code 
duplication?

Dirk

> Am 15.11.2023 um 14:28 schrieb Nir Lisker :
> 
>> 3D line and point primitives
> 
> I filed https://bugs.openjdk.org/browse/JDK-8316398 for this already. As 
> noted, it requires a somewhat complex computation for intersections and 
> possibly for contains. If you would like to write these Mesh classes, like 
> the current TriangleMesh, I can write the rest.
> 
>> removal of AWT
> 
> Isn't that *a lot* of work? All the image IO is AWT, no? 
> 
> On Wed, Nov 15, 2023 at 10:48 AM Dirk Lemmermann  > wrote:
>> Hi guys,
>> 
>> 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:
>> 
>> All I want for Christmas is … / what I think is needed for JavaFX going 
>> forward ...
>> 
>> - removal of AWT 
>> - a tray API (tray icon) 
>> - undecorated interactive stage style 
>> - blur support for stages 
>> - WebP image format support 
>> - native embedded browser (Chromium) 
>> - 3D line and point primitives 
>> - injection support in FXML for custom controls 
>> - TableView improvements, aka. TableView2
>> 
>> (order of items does not imply priority)
>> 
>> Dirk
>> 

Re: My JavaFX Christmas Wishlist

[Nir Lisker]

>
> 3D line and point primitives
>

I filed https://bugs.openjdk.org/browse/JDK-8316398 for this already. As
noted, it requires a somewhat complex computation for intersections and
possibly for contains. If you would like to write these Mesh classes, like
the current TriangleMesh, I can write the rest.

removal of AWT
>

Isn't that *a lot* of work? All the image IO is AWT, no?

On Wed, Nov 15, 2023 at 10:48 AM Dirk Lemmermann 
wrote:

> Hi guys,
>
> 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:
>
> All I want for Christmas is … / what I think is needed for JavaFX going
> forward ...
>
> - removal of AWT
> - a tray API (tray icon)
> - undecorated interactive stage style
> - blur support for stages
> - WebP image format support
> - native embedded browser (Chromium)
> - 3D line and point primitives
> - injection support in FXML for custom controls
> - TableView improvements, aka. TableView2
>
> (order of items does not imply priority)
>
> Dirk
>
>

Re: My JavaFX Christmas Wishlist

[Mark Raynsford]

On Wed, 2023-11-15 at 09:47 +0100, Dirk Lemmermann wrote:
> 
> All I want for Christmas is … / what I think is needed for JavaFX
> going forward ...

Is it sad that all I really want for Christmas is to be able to specify
that text under a certain size threshold shouldn't be antialiased? My
JavaFX console components look very blurry. :)

-- 
Mark Raynsford | https://www.io7m.com

My JavaFX Christmas Wishlist

[Dirk Lemmermann]

Hi guys,

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:

All I want for Christmas is … / what I think is needed for JavaFX going forward 
...

- removal of AWT 
- a tray API (tray icon) 
- undecorated interactive stage style 
- blur support for stages 
- WebP image format support 
- native embedded browser (Chromium) 
- 3D line and point primitives 
- injection support in FXML for custom controls 
- TableView improvements, aka. TableView2

(order of items does not imply priority)

Dirk