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 <tom.schi...@bestsolution.at> 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 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 Java window on screen? >> I don’t think the delay is long enough to bother with a splash screen these >> days. >> >> Scott >> >>> On Jun 3, 2018, at 4:22 AM, Tom Schindl <tom.schi...@bestsolution.at> wrote: >>> >>> That's why I requested that since a long time from the packager because >>> a splash has to be part of the native launcher created. >>> >>> The Eclipse-RCP-Launcher does exactly the right thing: >>> * Show a static image (IIRC they use bmp) >>> * Once the VM and UI-Toolkit is up replace that image with a window (SWT >>> calls it Shell) so that you can go interactive showing videos, >>> a progressbar, ... >>> >>> Tom >>> >>>> On 03.06.18 10:11, Mario Ivankovits wrote: >>>> A preloader/splash-screen will/should also hide the JVM startup time. >>>> >>>> Best regards, >>>> Mario >>>> >>>> >>>>> Am 03.06.2018 um 09:57 schrieb Tom Schindl <tom.schi...@bestsolution.at>: >>>>> >>>>> On 01.06.18 19:42, Johan Vos wrote: >>>>>> I'm not saying a preloader is really a requirement, but I know of a few >>>>>> applications that are using it and benefiting from it. >>>>>> >>>>>> The preloader functionality is more than just a splash screen, and I see >>>>>> this valuable for instance when static initializers of classes that are >>>>>> used in the main class may take a lot of time. >>>>> >>>>> Then I'd argue that you can easily refactor your main-class ;-) >>>>> >>>>> Tom >>>>
