+1 for CSS perf (diagnostic tooling for slow selectors like @Daniel Gloeckner
referenced earlier would also be a bonus)
+ for scene graph rendering perf
+ table perf
+ table features and fixes (column freezing, row span, selection model fixes
and memory leak fixes)
+ integration of controlsfx
Keeping WebKit as up-to-date with upstream as possible is the most
important thing for me personally.
Also upgrading the "org.w3c.dom" from HTML 4 to HTML 5 is a big one as
well. As an example,
the version of WebKit JavaFX uses supports "Document.querySelectorAll()"
which can be used via:
Hi Jonathan,
+1 to that list for me.
In my experience JavaFX performs well for the "low-level" (Canvas +
GraphicsContext) stuff with one exception - the PixelWriter APIs appear do
a lot of array duplication and copying under the hood which I believe can
be optimised. I'll investigate further and
Hi,
I agree the JavaFX team should focus on the core:
* CSS & SG Performance - Like Felix says this needs to be improved
significantly. It is unjustifable that JavaFX is lagging so much
behind Browsers and other UI-Toolkits
* WebGL support in WebView or a way to run Chromium as an external
Tom,
Can you dive into what you want to see in TableView? Performance
improvements, or some particular features?
Btw, I'd love to see someone in the community implement a flexbox
layout. It seems to be what I hear most about these days.
Finally - have you tested your custom layouts on JDK
From my perspective, from this list, TableView is a big candidate to get some
real TLC. And about animations; for testing it is very important to be able to
_easy_ detect when an animation is still active (one of the biggest problems I
currently have with CSS 3 animations).
About Layout
How about:
1. Greatly enhanced 3D support including (but not limited to) a 3D Canvas.
2. Significantly increased scene graph rendering performance (it may have been
done already).
3. Official mobile and embedded support (without having to rely on Gluon etc.,
even though they are doing a
Hi folks,
Development on JDK 9 is slowly starting to ramp down, and we are
starting to turn our attention to the goals for JavaFX in JDK 10 and
beyond. We are starting to compile our list of what we think is
important, but we really want to hear from the community about what
their highest
Please review this simple fix for MarlinFX:
JBS: https://bugs.openjdk.java.net/browse/JDK-8170879
webrev: http://cr.openjdk.java.net/~lbourges/marlinFX/marlinFX-8170879.0/
As mentioned in JBS, I studied both quality & performance and MarlinFX is
now slightly better than openpisces (1.6 vs 2.1
The fix applied cleanly to 8u-dev and fixed the same pair of bugs so this is
now also a backport request.
8u-specific webrev:
http://cr.openjdk.java.net/~flar/JDK-8088857/webrev.8u.rt.00/
...jim
On 12/7/16 8:06 AM, Jim Graham wrote:
JBS:
For scripting languages that possess javax.script (part of Java since Java
1.6/6!) implementations
the JavaFX infrastructure is of a great attractivity.
JavaFX would allow script programmers for creating platform independent GUIs to
take fully advantage
for their own purposes, i.e. "surfing on
On 28.11.2016 14:18, Rony G. Flatscher wrote:
> Dalibor,
>
> thank you very much for this link, just posted a comparable question there.
>
> Poking around the questions (many unanswered) posted there, my hopes are not
> very high to get an
> answer (maybe I am too pessimistic here)...
>
> Again,
JBS: https://bugs.openjdk.java.net/browse/JDK-8088857
webrev: http://cr.openjdk.java.net/~flar/JDK-8088857/webrev.rt.00/
Fix is as we discussed.
I'll investigate applying it to 8u-dev soon...
...jim
13 matches
Mail list logo