Unfortunately Apple is doing exactly what Microsoft did during the “Great API
Wars”. During this time, MS decided to go with its own exclusive graphics API
namely Direct 3D as part of their whole DirectX technology instead of the
obvious approach of supporting OpenGL fully.
These days, GPU
Apple has been making noises about this for a while. I wouldn't expect
them to drop OpenGL in the very near future, but it would seem that
investigating a Metal pipeline for FX is timely.
-- Kevin
On 6/4/2018 1:51 PM, Tom Schindl wrote:
Hi,
I don‘t know what the Apple guys are smoking but
Looks like Gluon has moved SceneBuilder from Bitbucket for GitHub.
https://github.com/gluonhq/scenebuilder
I like this move. GitHub is much better to work with.
Den fre. 27. apr. 2018 kl. 13:31 skrev Sverre Moe :
>
> I would like to hear from Gluon about their work on SceneBuilder.
> Do they
Hi,
I don‘t know what the Apple guys are smoking but they just deprecated OpenGL.
The question is what does this mean for JavaFX.
See https://developer.apple.com/macos/whats-new/
Tom
Von meinem iPhone gesendet
Hi!
I’ve just test with this very small JavaFX Application:
public class TstFx extends Application
{
@Override
public void start(Stage primaryStage) throws Exception
{
Label root = new Label("test");
Scene scene = new Scene(root, 800, 600);
Maybe I misunderstood the question but to my opinion the real question is
whether the new java packager has to provide the support for a splash screen
or not. This has nothing to do with the question whether applications should
have a splash screen or not because if we find that todays Java is
Nobody is arguing against splash screens. I’m simply suggesting that the JVM
startup is not slow enough that we need special handling of this in native code.
If Java can get a window displayed in under half a second there is no need for
the added complexity to support a native splash screen in
Hi,
I agree with Johan and others, a splash screen is valuable and needed.
Microsoft applications that run on Windows itself (think Word, Excel, etc),
they have a splash screen, Intelllij has a splash screen (it's swing based
AFAIK), etc.. If a Microsoft application running on its own operating
The problem is not the Java window, but the dependencies.
If that window is created by a class that requires resolving other classes
and somehow one of these classes take a long time to initialize, it will be
slow.
- Johan
On Mon, Jun 4, 2018 at 12:53 PM Scott Palmer wrote:
> If a Java window
If a Java window appears in less than half a second there is no point in adding
the complexity of a native splash screen.
Scott
> On Jun 4, 2018, at 5:13 AM, Tom Schindl wrote:
>
> A splash screen has to be that instant that it IMHO makes no sense to
> time how long it takes to get the JVM
A splash screen has to be that instant that it IMHO makes no sense to
time how long it takes to get the JVM and JavaFX up and running because
it can never be as instant as a splash has to show up.
Tom
On 04.06.18 01:06, Scott Palmer wrote:
> Has anyone actually timed how long it takes to get a
11 matches
Mail list logo
