|
|
|
|
|
| Re: How to show a splash image by launching RCP in the console? [message #451266 is a reply to message #451234] |
Tue, 20 June 2006 05:55   |
 Jason
Messages: 45
Registered: July 2009 |
Member |
|
|
Paul Webster wrote:
> Jason wrote:
>>
>>> Also, if you self-host an eclipse application and run it, you can
>>> check out the Debug View. The Properties of the process will give you
>>> the command line eclipse used to start up eclipse.
>>
>>
>>
>> What exactly does <command> stand for? Looks like it is a required
>> parameters.
>>
> Dunno, but if you selfhost and check the properties, it looks like the
> command line has -showSplash 600
> Later,
> PW
If I append -debug in the properties of the executable shortcut like
"C:\rcp\myrcp.exe" -debug
I can see the splash is shown and the debug info in the console as well:
runCommand:
<C:\rcp\myrcp.exe><-name><myrcp><-showsplash><600><c:\rcp\plugins\com.my.rcp.ui.base_1.0.2\splash.bmp >
And I run it in cmd line liek
java -cp startup.jar org.eclipse.core.launcher.Main -application
"com.my.rcp.ui.base.DashBoard" -showSplash 600 -dubug
The splash is not shown and the debug info in the console looks like:
runCommand:
<none><-name><none><-showsplash><600><c:\rcp\plugins\com.my.rcp.ui.base_1.0.2\splash.bmp >
It does not work even I specify -name.
So I followed the code in org.eclipse.core.launcher.Main; in its
runCommand and handleSplash method, there is some comment that looks like
only executable launcher is supported for splash.
and also I searched in the website, and found a post
https://bugs.eclipse.org/bugs/show_bug.cgi?id=81463 for the splash issue,
but it seems to have been resolved.
/*
* Handle splash screen.
* We support 2 startup scenarios:
*
* (1) the executable launcher put up the splash screen. In that
* scenario we are invoked with -endsplash command which is
* fully formed to take down the splash screen
*
* (2) the executable launcher did not put up the splash screen,
* but invokes Eclipse with partially formed -showsplash command.
* In this scenario we determine which splash to display (based on
* feature information) and then call -showsplash command.
*
* In both scenarios we pass a handler (Runnable) to the platform.
* The handler is called as a result of the launched application
calling
* Platform.endSplash(). In the first scenario this results in the
* -endsplash command being executed. In the second scenario this
* results in the process created as a result of the -showsplash
command
* being destroyed.
*
* @param defaultPath search path for the boot plugin
*/
private void handleSplash(URL[] defaultPath) {
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03719 seconds
] 
Search
Help
Register
Login
Home
