Draft JEP for new Packaging Tool (replacement for javapackager)
swpalmer at gmail.com
Tue Jun 5 15:46:47 UTC 2018
Yes, my only comment was that if we can get a window up using standard Java
GUI frameworks fast enough, then the complexity of adding splashscreen
support to the launcher isn't justified.
Mario's example shows that is it 1-2 seconds to get a window up. That is a
bit high. If it was under 1s then I would suggest not bothering, it isn't,
so keep it on the list of desired features.
On Tue, Jun 5, 2018 at 8:21 AM Pedro Duque Vieira <
pedro.duquevieira at gmail.com> wrote:
> Sorry, perhaps it was I who misunderstood the debate..
> On Mon, Jun 4, 2018 at 4:06 PM, Michael Paus <mp at jugs.org> wrote:
> > 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 fast
> > enough
> > to display a simple window in less than a second or so, then the Java GUI
> > (Swing or JavaFX) could provide a splash screen itself. There is then no
> > need
> > for an additional mechanism provided my the packager.
> > Am 04.06.18 um 16:44 schrieb Pedro Duque Vieira:
> > 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
> >> AFAIK), etc.. If a Microsoft application running on its own operating
> >> system needs a splash screen then chances are pretty high that there
> >> be Java apps that'll need a splash screen.
> >> Cheers,
> Pedro Duque Vieira
More information about the openjfx-dev