devilhorns pushed a commit to branch master.
commit 711a9c46905b73d8dc4ea198732d502b9d468eb5
Author: Chris Michael <[email protected]>
Date: Tue Aug 6 12:36:48 2013 +0100
Update desktop_shell xml file for version 2.
Signed-off-by: Chris Michael <[email protected]>
---
src/modules/wl_desktop_shell/e-desktop-shell.xml | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/src/modules/wl_desktop_shell/e-desktop-shell.xml
b/src/modules/wl_desktop_shell/e-desktop-shell.xml
index 0421eb5..50c343c 100644
--- a/src/modules/wl_desktop_shell/e-desktop-shell.xml
+++ b/src/modules/wl_desktop_shell/e-desktop-shell.xml
@@ -1,6 +1,6 @@
<protocol name="desktop">
- <interface name="e_desktop_shell" version="1">
+ <interface name="e_desktop_shell" version="2">
<request name="set_background">
<arg name="output" type="object" interface="wl_output"/>
<arg name="surface" type="object" interface="wl_surface"/>
@@ -21,6 +21,17 @@
<arg name="surface" type="object" interface="wl_surface"/>
</request>
+ <request name="desktop_ready" since="2">
+ <description summary="desktop is ready to be shown">
+ Tell the server, that enough desktop elements have been drawn
+ to make the desktop look ready for use. During start-up, the
+ server can wait for this request with a black screen before
+ starting to fade in the desktop, for instance. If the client
+ parts of a desktop take a long time to initialize, we avoid
+ showing temporary garbage.
+ </description>
+ </request>
+
<!-- We'll fold most of wl_shell into this interface and then
they'll share the configure event. -->
<event name="configure">
--
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
