-
Bug
-
Resolution: Won't Fix
-
P3
-
7
-
generic
-
generic
We should try to relaunch VM (if needed!) as early as possible to:
a) provide as smooth UE as possible (if progress disapears and then restarts from 0 it is confusing)
b) start faster - if we relaunch early then we do not even need to init UI toolkits, create preloader windows, etc.
Currently, in the case of plugin (webstart needs to be checked too) we initiate ralaunch after we load all jar in the loadJars().
However, most of conditions could be checked much earlier.
Ideal logic is along these lines:
- get all JNLP files
- if installers are null - check if we need relaunch
- if installers are not null - setup progress, get them, then check if they require relaunch and relaunch
- setup progress, load rest of jars
a) provide as smooth UE as possible (if progress disapears and then restarts from 0 it is confusing)
b) start faster - if we relaunch early then we do not even need to init UI toolkits, create preloader windows, etc.
Currently, in the case of plugin (webstart needs to be checked too) we initiate ralaunch after we load all jar in the loadJars().
However, most of conditions could be checked much earlier.
Ideal logic is along these lines:
- get all JNLP files
- if installers are null - check if we need relaunch
- if installers are not null - setup progress, get them, then check if they require relaunch and relaunch
- setup progress, load rest of jars