core: reimplement Wayland support #1267
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Utilized previous Wayland implementation as a base, but made the following changes:
Linux
andWayland
/X11
, then placed properties in more-or-less the correct place. e.g. properties that belong to Wayland are inWayland.zig
. Properties that belong to any Linux implementation belong inLinux.zig
. I did not do this perfectly, but it can be iterated on later (especially after X11 is implemented).Wayland
into the new event loopregistry_listener
for example) because all the listeners consist of one or more functions, and an actual listener with is an instance of a struct that holds pointers to those functions. The functions aren't used anywhere else, so it made sense to me to package the listener struct and it's functions together under one namespace. Each listener has it's own namespace.wl_proxy_set_tag
looked unnecessary becausewl.tag
was never set (which means maybenull
was getting passed in?) and it doesn't look to me like that tag was never used anywhere else to reference the surface.