Attachment #46820
Write about best-practices for interface names in the same place they're defined patch 2011-05-17 09:11:43 UTC 2.57 KB no flags Details
Attachment #46821
[PATCH 2/9] Formally define a unique connection name and a well-known bus name patch 2011-05-17 09:12:05 UTC 1.69 KB no flags Details
Attachment #46822
[PATCH 3/9] Describe best-practices for naming well-known bus names patch 2011-05-17 09:12:19 UTC 2.14 KB no flags Details
Attachment #46823
[PATCH 4/9] Describe conventional naming of methods and signals patch 2011-05-17 09:12:32 UTC 1.11 KB no flags Details
Attachment #46824
[PATCH 5/9] Describe conventional naming of errors patch 2011-05-17 09:12:48 UTC 1.20 KB no flags Details
Attachment #46825
[PATCH 6/9] Briefly mention why to namespace object-paths patch 2011-05-17 09:13:03 UTC 1.71 KB no flags Details
Attachment #46826
[PATCH 7/9] Remove the old, vague Naming Conventions section patch 2011-05-17 09:13:22 UTC 1.23 KB no flags Details
Attachment #46827
[PATCH 8/9] Describe best practices for property names, and recommend against dash-separated-words patch 2011-05-17 09:13:46 UTC 1.85 KB no flags Details
Attachment #46828
[PATCH 9/9] Cross-reference from the glossary to interface names etc. patch 2011-05-17 09:14:05 UTC 1.71 KB no flags Details
Attachment #126931
spec: Recommend against using ‘/’ for object paths patch 2016-10-01 11:27:20 UTC 1.72 KB no flags Details

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.