0.30.0 release roadmap

[elinorbgr]

Things to do and iterate on with alphas before the actual release

• prototype upgrade of SCTK -- Rework for wayland-rs 0.30 client-toolkit#215
• prototype upgrade of Smithay -- Rework wayland rs 0.30 smithay#454
• Full pass on documentation (including readmes)
  • wayland-sys
  • wayland-backend
  • wayland-scanner
  • wayland-client
  • wayland-server
  • wayland-egl
  • wayland-cursor
  • wayland-protocols
  • main readme of the repo
• deny unsafe_op_in_unsafe_fn
• split wayland-protocols into multiple crates
• 0.30 sys backend audit with valgrind #448
• server: don't require a DataInit initialization if the created object is already destroyed on callback return (for example if a protocol error was triggered) -- backend: allow server to omit ObjectData on error #458
• Remove generic argument from ClientData or provide state in its callbacks
• backend/client/sys: Backend::from_foreign_display #497
• Find a way to improve wayland-client's event_created_child!()
• Implement with_all_objects_for on the server/sys backend
• Investigate if DelegateDispatch can be fused with Dispatch : client/server: fuse DelegateDispatch into Dispatch #518
• Fix all remaining TODOs

And non-blocking, but overall useful thing to do: improve code coverage by writing more tests, see https://app.codecov.io/gh/Smithay/wayland-rs

[i509VCB]

We should probably set deny for the unsafe_op_in_unsafe_fn lint.

Fyi this is going to become default or already is in 2021 edition.

[i509VCB]

Pending a new release of nix to fix the sigpipe signal issue since the new constants are not in nix yet: #457

I think we could use libc though for now to temporarily fix that problem>

[elinorbgr]

It seems like a nix release might not be too far away? https://github.com/nix-rust/nix/milestone/9

[i509VCB]

split wayland-protocols into multiple crates

This has been done

[A6GibKm]

backend::sys::client::Backend::from_foreign_display()

Once this is in, how does one get the WlDisplay?. Or alternatively, if I start with a ptr to a wl_surface how do I make use of this api and get a WlSurface.

EDIT: in the particular case of the display, there is Connection::display so it is not a problem, but in general it might be problematic, see https://github.com/gtk-rs/gtk4-rs/blob/master/gdk4-wayland/src/wayland_device.rs#L52 for example where in multiple places we want to get something from a foreign ptr (steat, display, surface, monitor, etc).

[elinorbgr]

Once this is in, how does one get the WlDisplay?. Or alternatively, if I start with a ptr to a wl_surface how do I make use of this api and get a WlSurface.

You need at least a pointer to the wl_display alongside the pointer to the wl_surface. Then:

• Using Backend::from_foreign_display, you can create a Backend from the *mut wl_display, and create a Connection from that backend using the From impl.
• You can then use ObjectId::from_ptr to get an ObjectId from the *mut wl_surface
• And finally use <WlSurface as Proxy>::from_id to get the WlSurface

From that, the only missing part is Backend::from_foreign_display, the rest already exists.

[l4l]

Is there any migration guide for 0.29.* to the current version?

[elinorbgr]

There is no proper guide (yet), but you can refer to this comment for an overview of what changed