When you have control over the framework your application runs in, you
could also patch the felix.jar to include an image and the
SplashScreen-Image manifest entry. Note that this only works in Java
6, though.
Angelo
On 4 Dec 2008, at 13:54, Rob Walker wrote:
Unfortunately ours isn't very generalised - and is internal rather
than
open source, but I can tell you how we made it work (it isn't exactly
clever)
- splash and property handlers are the only bundles register on start
level 1 of our framework, so they come up first.
- we use servicebinder, and our splash Impl in activate() instatiates
the splash screen and registers bundle and framework listeners
- the splash itself works out how many other bundles will be installed
and started and uses this to create our progress bar.
- as each bundle event comes in it marches the progress bar on 1 step,
and adds a text with the name of saying "installed/started" + the
bundle
name
- when the splash sees the framework started event it tears itself
down
and clears listeners
- at roughly the same time our "main frame" will also see the
framework
started event and display itself
That's about it really - pretty simple.
-- Rob
meinc wrote:
Does anyone know about a common OSGi SplashScreen Bundle ?
--
Ascert - Taking systems to the Edge
[EMAIL PROTECTED]
+44 (0)20 7488 3470
www.ascert.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
