Improves the outputmanagement and outputdevice protocol documentation.
Details
Details
- Reviewers
davidedmundson - Group Reviewers
Frameworks - Commits
- R127:272112a07f07: Improve protocols documentation
Diff Detail
Diff Detail
- Repository
- R127 KWayland
- Branch
- improveOutputManagementDoc
- Lint
No Linters Available - Unit
No Unit Test Coverage
Comment Actions
Currently I'm reading through these protocols for my 5.13 color correction work and I was wondering about the output management related protocol documentation, which seems to me faulty in many areas. Please take into account that I haven't yet written on any Wayland protocols when reviewing my changes.
| src/client/protocols/outputdevice.xml | ||
|---|---|---|
| 67 ↗ | (On Diff #30673) | earlier you changed all the "compositor" to "server" |
| 160 ↗ | (On Diff #30673) | you've changed 1/2 properties ->events tbh, properties was fine, everything is events in wayland terms,but semantically they're still properties and it separates them from the "done" event |
| src/client/protocols/outputdevice.xml | ||
|---|---|---|
| 67 ↗ | (On Diff #30673) | The usage of terms compositor and server is not clearly regulated in the Wayland world besides that these terms describe the same "application" (for example KWin). I try to use "server" whenever I talk about this application communicating with clients and "compositor" whenever I talk about this application in its capability of arranging surfaces to a final output image. |