Starting to add comments from the XDG spec
Getty Ritter
6 years ago
115 | 115 | |
116 | 116 | #[derive(Debug)] |
117 | 117 | pub struct DesktopEntryInfo { |
118 | /// Version of the Desktop Entry Specification that the desktop | |
119 | /// entry conforms with. Entries that confirm with this version of | |
120 | /// the specification should use `1.1`. Note that the version | |
121 | /// field is not required to be present. | |
118 | 122 | pub version: Option<String>, |
123 | /// Specific name of the application, for example "Mozilla". | |
119 | 124 | pub name: String, |
125 | /// Generic name of the application, for example "Web Browser". | |
120 | 126 | pub generic_name: Option<String>, |
127 | /// `NoDisplay` means "this application exists, but don't display | |
128 | /// it in the menus". This can be useful to e.g. associate this | |
129 | /// application with MIME types, so that it gets launched from a | |
130 | /// file manager (or other apps), without having a menu entry for | |
131 | /// it (there are tons of good reasons for this, including | |
132 | /// e.g. the `netscape -remote`, or `kfmclient openURL` kind of | |
133 | /// stuff). | |
121 | 134 | pub no_display: bool, |
135 | /// Tooltip for the entry, for example "View sites on the | |
136 | /// Internet". The value should not be redundant with the values | |
137 | /// of `Name` and `GenericName`. | |
122 | 138 | pub comment: Option<String>, |
139 | /// Icon to display in file manager, menus, etc. If the name is an | |
140 | /// absolute path, the given file will be used. If the name is not | |
141 | /// an absolute path, the algorithm described in the Icon Theme | |
142 | /// Specification will be used to locate the icon. | |
123 | 143 | pub icon: Option<String>, |
124 | 144 | pub hidden: bool, |
125 | 145 | pub only_show_in: Vec<String>, |