On Tuesday 08 August 2006 04:35, Bastian, Waldo wrote:
> I will propose patches to the spec for review for these issues over the
> course of this week. If there are additional issues that should be
> clarified before the "1.0" release, please speak up now. Goal of the 1.0
> spec is to reflect existing practice by current implementations.

 While reading the spec I noticed a problem with the keys from the startup 
notification spec ("If true" for a string key which doesn't make sense). It 
comes from the spec itself, I have no idea how that managed to slip through, 
probably a copy&paste mistake. Additionally I'd like to make the description 
of StartupNotify= somewhat more explicit.

-- 
Lubos Lunak
KDE developer
---------------------------------------------------------------------
SuSE CR, s.r.o.  e-mail: [EMAIL PROTECTED] , [EMAIL PROTECTED]
Drahobejlova 27  tel: +420 2 9654 2373
190 00 Praha 9   fax: +420 2 9654 2374
Czech Republic   http://www.suse.cz/
--- desktop-entry-spec.xml.sav	2006-08-08 13:58:25.000000000 +0200
+++ desktop-entry-spec.xml	2006-08-08 16:58:18.000000000 +0200
@@ -540,8 +540,12 @@
 	    <entry id="key-startupnotify"><varname>StartupNotify</varname></entry>
 	    <entry>
 			If true, it is KNOWN that the application will send a "remove"
-			message when started with the <envar>DESKTOP_LAUNCH_ID</envar> environment variable
-			set (see the <ulink url="http://www.freedesktop.org/Standards/startup-notification-spec";>Startup Notification Protocol Specification</ulink> for more details).
+			message when started with the DESKTOP_LAUNCH_ID environment variable set.
+			If false, it is KNOWN that the application does not work
+			with startup notification at all (does not shown any window, breaks
+			even when using StartupWMClass, etc.).
+			If absent, a reasonable handling is up to implementations (assuming false,
+			using StartupWMClass, etc.). (See the <ulink url="http://www.freedesktop.org/Standards/startup-notification-spec";>Startup Notification Protocol Specification</ulink> for more details).
 	    </entry>
 	    <entry>boolean</entry>
 	    <entry>NO</entry>
@@ -551,7 +555,7 @@
 	  <row>
 	    <entry id="key-startupwmclass"><varname>StartupWMClass</varname></entry>
 	    <entry>
-			If true, it is KNOWN that the application will map at least one
+			If specified, it is known that the application will map at least one
 			window with the given string as its WM class or WM name hint (see the <ulink url="http://www.freedesktop.org/Standards/startup-notification-spec";>Startup Notification Protocol Specification</ulink> for more details).
 	    </entry>
 	    <entry>string</entry>
--- startup-notification.txt.sav	2006-02-07 13:48:29.000000000 +0100
+++ startup-notification.txt	2006-08-08 16:58:22.000000000 +0200
@@ -343,10 +343,15 @@ StartupNotify=BOOLEAN
   If true, it is KNOWN that the application will send a "remove"
   message when started with the DESKTOP_LAUNCH_ID environment variable
   set.
+  If false, it is KNOWN that the application does not work
+  with startup notification at all (does not shown any window, breaks
+  even when using StartupWMClass, etc.).
+  If absent, a reasonable handling is up to implementations (assuming false,
+  using StartupWMClass, etc.).
 
 StartupWMClass=STRING
 
-  If true, it is KNOWN that the application will map at least one
+  If specified, it is KNOWN that the application will map at least one
   window with the given string as its WM class or WM name hint.
 
 EWMH spec extensions
_______________________________________________
xdg mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/xdg

Reply via email to