-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
handbook/wayland: improve synopsis readability #287
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -50,11 +50,11 @@ endif::[] | |
|
||
[[wayland-synopsis]] | ||
== Wayland Synopsis | ||
Wayland is a new display server, but it differs from Xorg in several important ways. | ||
First, Wayland is only a protocol that acts as an intermediary between clients using a different mechanism which removes the dependency on an X server. | ||
Xorg includes both the X11 protocol, used to run remote displays and the X server will accept connections and display windows. | ||
Under Wayland, the compositor or window manager provides the display server instead of a traditional X server. | ||
Wayland is a communication protocol that can replace a display server such as Xorg. It differs from Xorg in several important ways. | ||
|
||
First, Wayland is only a protocol that acts as an intermediary between clients using a mechanism which removes the dependency on an X server. | ||
Xorg includes both the X11 protocol, used to run remote displays, and the X server, used to accept connections and display windows. | ||
Under Wayland, the compositor or window manager provides the display server instead of a traditional X server. | ||
Since Wayland is not an X server, traditional X screen connections will need to utilize other methods such as VNC or RDP for remote desktop management. | ||
Second, Wayland can manage composite communications between clients and a compositor as a separate entity which does not need to support the X protocols. | ||
Comment on lines
+53
to
59
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. i really like the suggestions, flow a little nicer than the previous version. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. They absolutely flow nicer than before. My suggestion is just a suggestion, and it is an honor for me to be here. That said, please look at the introductory paragraph of the synopsis of every preceding chapter. |
||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, that didn't work. What I was suggesting is to revert proposed changes to the README entirely.
The current state of the PR damages the tree by changing the blame for line 9.
EDIT: and please don't credit me, I absolutely did not coauthor any of this.