P1
If applet fails to start this is not visible to the end user.
We need to provide a way for deployer of FX apps to detect failures and be able to notify users appropriately.
Type of failures to support:
1) no suitable JRE (this is done)
2) not supported OS (js check)
3) not supported broswer (js check)
4) blocked by firewall (optional)
5) security permissions were not given (in the applet launcher)
6) failed to start for some other reason
We should also hide overlay of start takes too long. It could be error behind the app window.
Depending on what will be typical start it could be 90 or 120s by default. May be overridable as javafx() parameter?
Apparently Vanoc app needs to support English & French and this seems to be applicable to error messages too.
We need to provide simple (unadvertised?) way to customize them. Perhaps pass "messages" map as part of the parameters. It is set them use messages from this map instead of hardcoded english messages.
We need to provide a way for deployer of FX apps to detect failures and be able to notify users appropriately.
Type of failures to support:
1) no suitable JRE (this is done)
2) not supported OS (js check)
3) not supported broswer (js check)
4) blocked by firewall (optional)
5) security permissions were not given (in the applet launcher)
6) failed to start for some other reason
We should also hide overlay of start takes too long. It could be error behind the app window.
Depending on what will be typical start it could be 90 or 120s by default. May be overridable as javafx() parameter?
Apparently Vanoc app needs to support English & French and this seems to be applicable to error messages too.
We need to provide simple (unadvertised?) way to customize them. Perhaps pass "messages" map as part of the parameters. It is set them use messages from this map instead of hardcoded english messages.