Changes: splash screen specification added to README

RevBy: Pertti Kellomaki

README

@@ -14,8 +14,11 @@ preloading dynamically linked libraries and caching stuff
 (MComponentCache, MDeclarativeCache). It also saves memory, because
 all launched applications share certain resources.
 
-There's also an option to efficiently launch applications as single instances 
-(see 2.3).  
+In addition to the fast launch, applauncherd enables
+
+* a simple single-instance support for applications (see 2.3)
+
+* showing a splash screen during the launch (see 2.4)
 
 Technical overview
 ==============================
@@ -309,6 +312,32 @@ Note, that in this case the launcher is not used.
 Consider using --single-instance instead of the single instance functionality
 provided by D-Bus, because it very likely is much faster.
 
+2.4 Splash screen
+
+Applauncherd supports showing a splash screen if there is mcompositor
+(the MeeGo window manager) running.
+
+The splash screen is not shown by default. If an application wants it
+to be shown, it must pass --splash, and optionally --splash-landscape
+arguments to the invoker.
+
+For instance,
+
+/usr/bin/invoker --splash=/usr/share/application_name/splash.jpg \
+		 --splash-landscape=/usr/share/application_name/splash-l.jpg \
+		 --type=m \
+		 /usr/bin/application_name
+
+shows the splash screen with splash.jpg as its content when the device
+is in the portrait orientation. Otherwise splash-l.jpg is shown. If
+only --splash is given, that image is shown in both orientations.
+
+Invoker passes the splash request to the booster. The booster sends
+the splash request to the window manager by setting a window property
+to window manager's window.
+
+If the filenames do not include absolute paths, the window manager
+looks for the files from a default location.
  
 3. STARTING APPLAUNCHERD