Skip to content
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

Rework for wayland-rs 0.30 #215

Merged
merged 130 commits into from
Jul 17, 2022
Merged

Rework for wayland-rs 0.30 #215

merged 130 commits into from
Jul 17, 2022

Conversation

elinorbgr
Copy link
Member

@elinorbgr elinorbgr commented Jan 5, 2022

Roadmap from i5 for 0.30:

@i509VCB
Copy link
Member

i509VCB commented Mar 23, 2022

Just going to note here to keep this idea in our minds.

Do we want to offer a sort of "super delegate type" for desktop like the environment desktop preset in 0.29 era sctk.

One way this could be represented using a sort of DesktopState type which itself contains multiple delegate types (compositor, xdg shell, output, seat) and a single macro to delegate to that group of delegate types.

You would still need to implement some traits but it would make some very common groups of protocols easily usable.

@i509VCB
Copy link
Member

i509VCB commented Apr 15, 2022

Do we want to consider more types of shm pools.

A double buffered pool is already essentially guaranteed to be implemented

There are some other possible useful pools implementations I can think of:

  • SinglePool (name needs bikeshed) - A single shm buffer, meant for maximum control with race free access to the underlying content. This may be useful in very specific scenarios. This would not be implemented using a MultiPool as to reduce the overhead as much as possible.
  • SwapchainPool (with name bikeshed) - Acts like a swapchain with N-buffering. This might be hard to justify since you would struggle to use the buffers faster than the server renders to the screen unless very aggressive damage tracking is used. Resizes could balloon really quickly due to the shear number of buffers. Might be useful for high refresh rate displays.

@elinorbgr
Copy link
Member Author

Overall, I think those additional pools should not be considered as blocking the 0.30 update, and can be added after the merge.

@i509VCB i509VCB marked this pull request as ready for review July 17, 2022 02:51
Copy link
Member

@i509VCB i509VCB left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This branch is being merged into master. All pending issues will have issues created and added to a milestone group.

@i509VCB i509VCB merged commit 3f8dc7c into master Jul 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants