I don´t see what the big annoyance is. A splash screen reminds you
that the program is loading.
A question is how the splash screen is implemented in Jitsi. Sun
introduced in Java 6 an API for specifying a splash screen, which as
far as I remember means that you include a JPG file in the jar, and a
parameter in the manifest file, and such splash screen is shown
IMMEDIATELY, without waiting for the JRE to load and the classes to
initialize. In other words, one of the major complaints of Java apps
and splash screen before it was that it took too much time between
"double clicking" the app icon and the splash screen showing, so the
implemented it that way.
If that is the API that Jitsi uses for the splash screen, then I don´t
know if a parameter is provided to not show it... my guess is that it
In other words, ¨fixing" this non-annoyance for this user would meant
NOT using the Splash Screen API and all the benefits it provides
(instant showing of the splash screen, offseting the program load
annoyance for the user by providing visual feedback of what is going
My vote would be: please don´t fix a non-issue
On Tue, Jun 10, 2014 at 2:37 AM, Emil Ivov <firstname.lastname@example.org> wrote:
If someone is interested in looking into this, adding a command line param
(e.g., nosplash) and using it for autostart sounds like the way to do it.
During times of Universal Deceit, telling the truth becomes a revolutionary act
Durante épocas de Engaño Universal, decir la verdad se convierte en un
- George Orwell