Home » Eclipse Projects » Eclipse Platform » splash screen problem
| splash screen problem [message #125533] |
Tue, 09 September 2003 11:00  |
Eclipse User |
|
|
|
Hi
When we execute eclipse through batch file, I am not getting splash screen.
Please help me.
Thanks,
MorPheus
|
|
| | |
| Re: splash screen problem [message #126541 is a reply to message #126320] |
Wed, 10 September 2003 11:11  |
| Eclipse User |
|
|
|
Originally posted by: dorian.birsan.net
Chris has already answered it, it is the eclipse.exe that displays the
splash screen, but you are bypassing eclipse.exe by calling the Main class
directly.
-Dorian
"Smith" <mmahudeeswaran@selectica.com> wrote in message
news:bjms8f$5p7$1@eclipse.org...
> yes, obviously it launches the virtual machine,
> because the contents of my batch file is
>
> java -classpath startup.jar org.eclipse.core.launcher.Main
>
> Everything is working except the splash screen.
>
> Please help
>
> Regards,
> Smith
>
>
> "Chris Laffra" <Chris_Laffra@oti.com> wrote in message
> news:bjktcc$93o$1@eclipse.org...
> > The splash screen is shown by the eclipse.exe program.
> > This program launches the VM (does what your batch file does).
> > It also listens to the VM process. If it returns with a restart request
> > the VM is restarted (happens when update manager is run).
> > If the VM crashes, the exe presents you with the famous (and not
> > really helpful) message to check the .log file in your workspace.
> > If it is really so smart, why doesn't it show the log file to me???
> >
> > Chris
> >
> > "MorPheus" <rgurupackiam@selectica.com> wrote in message
> > news:bjkplt$4mq$2@eclipse.org...
> > > Hi
> > >
> > > When we execute eclipse through batch file, I am not getting splash
> > screen.
> > > Please help me.
> > >
> > > Thanks,
> > > MorPheus
> > >
> > >
> >
> >
>
>
|
|
|
| Re: splash screen problem [message #126662 is a reply to message #126541] |
Wed, 10 September 2003 13:39 |
| Eclipse User |
|
|
|
Originally posted by: muelleimer.usenet.katzien.de
Hallo!
* dorian birsan <dorian@birsan.net> wrote:
> Chris has already answered it, it is the eclipse.exe that displays the
> splash screen, but you are bypassing eclipse.exe by calling the Main class
> directly.
Actually (at least if I've read the code right), the sequence is:
* eclipse starts java and sets the 'splash' options
* java startup of eclipse, splash handler is called via
System.something()
* splash handler puts up the splashscreen
* splash prozess is killed, when eclipse has started up.
The only thing is, that 'eclipse(.exe)' is startup and splash screen
handler in one. On linux, you can observe it via repeated 'ps aux |grep
eclipse' calls during startup.
So, do this call:
java -cp ... Main -showsplash "$ECLIPSE_DIR/eclipse.exe -showsplash 600"
(note the quotes: '$ECLIPSE_DIR/eclipse.exe -showsplash 600' must be one
string!)
That's at least how I do it in the debian startscript for eclipse,
which uses the binary launcher only for splash screen.
Jan
|
|
|
| Re: splash screen problem [message #127065 is a reply to message #126662] |
Wed, 10 September 2003 21:12 |
| Eclipse User |
|
|
|
Originally posted by: dorian.birsan.net
"Jan Schulz" <muelleimer@usenet.katzien.de> wrote in message
news:slrnbluoe3.8nq.muelleimer@snoopy.katzien.de...
> Hallo!
>
> * dorian birsan <dorian@birsan.net> wrote:
> > Chris has already answered it, it is the eclipse.exe that displays the
> > splash screen, but you are bypassing eclipse.exe by calling the Main
class
> > directly.
>
> Actually (at least if I've read the code right), the sequence is:
> * eclipse starts java and sets the 'splash' options
> * java startup of eclipse, splash handler is called via
> System.something()
> * splash handler puts up the splashscreen
> * splash prozess is killed, when eclipse has started up.
>
> The only thing is, that 'eclipse(.exe)' is startup and splash screen
> handler in one. On linux, you can observe it via repeated 'ps aux |grep
> eclipse' calls during startup.
>
> So, do this call:
> java -cp ... Main -showsplash "$ECLIPSE_DIR/eclipse.exe -showsplash 600"
> (note the quotes: '$ECLIPSE_DIR/eclipse.exe -showsplash 600' must be one
> string!)
I think this works only when the configuration (.config) exists and no
(implicit) restart is needed.
I've been wrong before, so I don't claim this is correct :-)
-Dorian
>
> That's at least how I do it in the debian startscript for eclipse,
> which uses the binary launcher only for splash screen.
>
> Jan
|
|
|
| Re: splash screen problem [message #127104 is a reply to message #127065] |
Wed, 10 September 2003 22:11 |
| Eclipse User |
|
|
|
Originally posted by: muelleimer.usenet.katzien.de
Hallo!
* dorian birsan <dorian@birsan.net> wrote:
>> java -cp ... Main -showsplash "$ECLIPSE_DIR/eclipse.exe -showsplash 600"
>> (note the quotes: '$ECLIPSE_DIR/eclipse.exe -showsplash 600' must be one
>> string!)
> I think this works only when the configuration (.config) exists and no
'.config'? You mean '.metadata' and subdirs? I just tested it with
'eclipse -data test' and it works like a charm: first the 'completing
install' and then the normal splash and eclipse window coming up.
..metatdata/.config/platform.cfg* was also there afterwards, showing
everything I expected.
> (implicit) restart is needed.
I've code in the startscript, which handles that. Basicly I've done a
rewrite of the eclipse launcher. This was needed to provide a
'eclipse-platform' package, which does not depend on any widget
toolkit (only 'Suggests:'). The splash screen may fail, but eclipse will
still be started up, if only motif libs are available (eclipse is
compiled with '-ws gtk').
I also needed to integrate a $HOME/.eclipse/eclipsrc, which handles some
default values for vmargs, data, window toolkit and some other things,
so that a menu entry can be used.
> I've been wrong before, so I don't claim this is correct :-)
As far as my testing goes, everything works. The only thing I
couldn't figure out yet was the '-install <path to eclipse>' option.
I've seen that a few times, but I couldn't reproduce it. Its not in
the C code (plugins/platform-launcher/library/eclipse.c)... Any ideas?
Jan
|
|
|
| Re: splash screen problem [message #127687 is a reply to message #127104] |
Thu, 11 September 2003 15:38 |
| Eclipse User |
|
|
|
Originally posted by: dorian.birsan.net
"Jan Schulz" <muelleimer@usenet.katzien.de> wrote in message
news:slrnblvmeg.3ld.muelleimer@snoopy.katzien.de...
> Hallo!
>
> * dorian birsan <dorian@birsan.net> wrote:
> >> java -cp ... Main -showsplash "$ECLIPSE_DIR/eclipse.exe -showsplash
600"
> >> (note the quotes: '$ECLIPSE_DIR/eclipse.exe -showsplash 600' must be
one
> >> string!)
> > I think this works only when the configuration (.config) exists and no
>
> '.config'? You mean '.metadata' and subdirs? I just tested it with
> 'eclipse -data test' and it works like a charm: first the 'completing
> install' and then the normal splash and eclipse window coming up.
> .metatdata/.config/platform.cfg* was also there afterwards, showing
> everything I expected.
I meant the .config directory which used to be inside .metadata, but it is
now (in M3) relocated to the install directory or some place under the
user's home (this work is not finished yet:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=37686).
However, as you describe the end result, you've been running an older
driver, so the above comment does not apply.
However, I have tried this on Windows and, with a brand new install, only
the "completing install" shows up, but not the eclipse splashscreen. The
splash showed up fine in the next invocation (once the .config was there).
>
> > (implicit) restart is needed.
>
> I've code in the startscript, which handles that. Basicly I've done a
> rewrite of the eclipse launcher. This was needed to provide a
> 'eclipse-platform' package, which does not depend on any widget
> toolkit (only 'Suggests:'). The splash screen may fail, but eclipse will
> still be started up, if only motif libs are available (eclipse is
> compiled with '-ws gtk').
>
> I also needed to integrate a $HOME/.eclipse/eclipsrc, which handles some
> default values for vmargs, data, window toolkit and some other things,
> so that a menu entry can be used.
Nice work!
>
> > I've been wrong before, so I don't claim this is correct :-)
>
> As far as my testing goes, everything works. The only thing I
> couldn't figure out yet was the '-install <path to eclipse>' option.
> I've seen that a few times, but I couldn't reproduce it. Its not in
> the C code (plugins/platform-launcher/library/eclipse.c)... Any ideas?
>
What doesn't work?
> Jan
|
|
|
| Re: splash screen problem [message #127766 is a reply to message #127687] |
Thu, 11 September 2003 18:27 |
| Eclipse User |
|
|
|
Originally posted by: muelleimer.usenet.katzien.de
Hallo!
* dorian birsan <dorian@birsan.net> wrote:
> I meant the .config directory which used to be inside .metadata, but it is
> now (in M3) relocated to the install directory or some place under the
> user's home (this work is not finished yet:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=37686).
Just to get to know what work will be ahead:
* is now the binary starter given some more 'responsibility', which I
can easily emulate?
* Is there a document describing what's going on internaly? Code
comments, which I can checkout?
* will it be possible to specify some default values (like the described
workspace, ws, vmargs), so that eclipse can be started up from a
menu entry?
It would be nice however if the 'starter' code would be seperated from
the 'splash scree code'. Messages like the 'Error:...' could also be
handled by a XWindow call.
> However, as you describe the end result, you've been running an older
> driver, so the above comment does not apply.
2.1.1 I'm still waiting for the main API changes in RCP before I start
packaging eclipse 3.0.
> However, I have tried this on Windows and, with a brand new install, only
> the "completing install" shows up, but not the eclipse splashscreen. The
> splash showed up fine in the next invocation (once the .config was there).
So it seems that I have to check whether tehr is already a workspace
there, add a option if not, and go on starting :) Hope thats all...
>> I also needed to integrate a $HOME/.eclipse/eclipsrc, which handles some
>> default values for vmargs, data, window toolkit and some other things,
>> so that a menu entry can be used.
> Nice work!
Thanks!
>> As far as my testing goes, everything works. The only thing I
>> couldn't figure out yet was the '-install <path to eclipse>' option.
>> I've seen that a few times, but I couldn't reproduce it. Its not in
>> the C code (plugins/platform-launcher/library/eclipse.c)... Any ideas?
> What doesn't work?
Nothing doesn't work, so I'm curious, what I miss :)
Jan
|
|
|
| Re: splash screen problem [message #128191 is a reply to message #127766] |
Fri, 12 September 2003 10:27 |
| Eclipse User |
|
|
|
Originally posted by: dorian.birsan.net
"Jan Schulz" <muelleimer@usenet.katzien.de> wrote in message
news:slrnbm1tls.24u.muelleimer@snoopy.katzien.de...
> Hallo!
>
> * dorian birsan <dorian@birsan.net> wrote:
> > I meant the .config directory which used to be inside .metadata, but it
is
> > now (in M3) relocated to the install directory or some place under the
> > user's home (this work is not finished yet:
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=37686).
>
> Just to get to know what work will be ahead:
> * is now the binary starter given some more 'responsibility', which I
> can easily emulate?
> * Is there a document describing what's going on internaly? Code
> comments, which I can checkout?
> * will it be possible to specify some default values (like the described
> workspace, ws, vmargs), so that eclipse can be started up from a
> menu entry?
Jan, I'd suggest you'd raise these questions on one of the developer's
mailing lists, such as platform-dev@eclipse.org or
platform-core-dev@eclipse.org , so it is more likely someone who's directly
involved with the startup code can answer.
>
> It would be nice however if the 'starter' code would be seperated from
> the 'splash scree code'. Messages like the 'Error:...' could also be
> handled by a XWindow call.
>
> > However, as you describe the end result, you've been running an older
> > driver, so the above comment does not apply.
>
> 2.1.1 I'm still waiting for the main API changes in RCP before I start
> packaging eclipse 3.0.
>
> > However, I have tried this on Windows and, with a brand new install,
only
> > the "completing install" shows up, but not the eclipse splashscreen. The
> > splash showed up fine in the next invocation (once the .config was
there).
>
> So it seems that I have to check whether tehr is already a workspace
> there, add a option if not, and go on starting :) Hope thats all...
>
> >> I also needed to integrate a $HOME/.eclipse/eclipsrc, which handles
some
> >> default values for vmargs, data, window toolkit and some other things,
> >> so that a menu entry can be used.
> > Nice work!
>
> Thanks!
>
> >> As far as my testing goes, everything works. The only thing I
> >> couldn't figure out yet was the '-install <path to eclipse>' option.
> >> I've seen that a few times, but I couldn't reproduce it. Its not in
> >> the C code (plugins/platform-launcher/library/eclipse.c)... Any ideas?
> > What doesn't work?
>
> Nothing doesn't work, so I'm curious, what I miss :)
Sorry, can't help, I am not familiar with it.
-Dorian
>
> Jan
|
|
|
Goto Forum:
Current Time: Sat May 03 17:55:29 EDT 2025
Powered by FUDForum. Page generated in 0.04419 seconds |
Home