Re: Draft JEP for new Packaging Tool (replacement for javapackager)
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 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 : >>> >>> 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 >>
Re: Draft JEP for new Packaging Tool (replacement for javapackager)
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 : >> >> 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 >
Re: Draft JEP for new Packaging Tool (replacement for javapackager)
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 : > > 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
Re: Draft JEP for new Packaging Tool (replacement for javapackager)
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
