[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Follow-up on splash-screen questions
- From: "Alex Blewitt" <alex.blewitt@xxxxxxxxx>
- Date: Wed, 14 Feb 2007 00:57:44 +0000
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YhXcvzu4JonQ46JlTMKOt8kElZP7nEou4ilOWWSf2QCZo1CbdYWK/AEtcLXs+Z54hAH/mSPFuxHoGTUhLMajH+Se5p1IUl1T+H/1f7qLYxheKAwqnVZGF64wmdZFuzlgmnCoo/GhkwQ7W8wFHLdouEBD2o2zZyDGyBjkhqo8eKg=
If you start Swing first on a Mac OS X system, you cannot start SWT
afterwards. Java WebStart of an SWT app fails for this reason on Mac
OS X at the moment; the (Apple) JWS code kicks off a Swing dialog,
which then prevents any SWT-based app from running.
Having a Swing splash would be a no-no.
On 13/02/07, Thomas Hallgren <thomas@xxxxxxx> wrote:
As a side-track on https://bugs.eclipse.org/bugs/show_bug.cgi?id=173742
I raised the question why the splash-screen is not handled completely by
Java. I'd like to continue that discussion here.
Andrew Niefer wrote:
> Thomas, the splash screen work was about more than simply displaying a graphic.
> We wanted to use SWT widgets in the splash screen, otherwise we would have
> just stayed with the old splash story (which is separate from this discussion
> about startup.jar). See
> and bug 161569 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=161569> for details of the investigations.
I thought the initial splash screen was a graphical image only. I
realize that it gets more complicated when you need to pass a native
handle to SWT classes booted at a later time. Using pure Java for the
splash would probably rule out the use of SWT widgets.
> Time-to-splash was a major consideration. On a cold machine (just turned on,
> no disk cache) the old splash method took around 6 seconds. Showing a graphic
> in java would have been about the same. For a properly setup eclipse using JNI
> to start the vm, the new launchre takes about 400ms on a cold start. (50ms on a
> warm start).
My reaction was to Pascals statement that Java is too damn slow for a
splash. I've tried various things on different machines, including
cold-start and clearmem.exe. I never get times anywhere near the 7781ms
reported for the "Funky Classloader" in comment #17. So question is, how
much of that time can be contributed to the use of SWT?
equinox-dev mailing list