Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
dev:session-management [2009/07/19 14:21] – fix some typos 67.188.6.70 | dev:session-management [2009/07/19 14:26] – more typos, localization note kelnos |
---|
==== Other Issues ==== | ==== Other Issues ==== |
| |
=== Value of the ''Name'' Key === | === Value of the Name Key === |
| |
The ''Name'' key in the desktop file would provide a user-readable name for the application. This is useful in a session editor (which ends up being the autostart editor). For autostart/session files installed by the application, this is already taken care of us, and the names are even probably localized for us. | The ''Name'' key in the desktop file would provide a user-readable name for the application. This is useful in a session editor (which ends up being the autostart editor). For autostart/session files installed by the application, this is already taken care of for us, and the names are even probably localized for us. |
| |
But for apps started by the user that get saved in the session, how do we figure out a useful value to put in the ''Name'' key? | But for apps started by the user that get saved in the session, how do we figure out a useful value to put in the ''Name'' key? |
Options: | Options: |
- Use the value of the SmProgram XSMP property if present. | - Use the value of the SmProgram XSMP property if present. |
- Dig around in the system and user .desktop file directories (''$XDG_DATA_DIRS/applications'') and try to find an application with a matching ''Exec'' key (or at least one with the same argv[0]), and use the ''Name'' key from there. | - Dig around in the system and user .desktop file directories (''$XDG_DATA_DIRS/applications'') and try to find an application with a matching ''Exec'' key (or at least one with the same argv[0]), and use the (probably localized) ''Name'' key from there. |
- When the session is saved, find the WM_CLIENT_LEADER window and take its _NET_WM_NAME property. This is also beneficial to allow the user to uniquely identify each entry if several copies of the same app are saved to the session. Usually this value will be localized as well. | - When the session is saved, find the WM_CLIENT_LEADER window and take its _NET_WM_NAME property. This is also beneficial to allow the user to uniquely identify each entry if several copies of the same app are saved to the session. Usually this value will be localized as well. |
| |