QtCS 2018: Wayland topics: Difference between revisions
Jump to navigation
Jump to search
Johanhelsing (talk | contribs) m (→Compositor) |
Johanhelsing (talk | contribs) mNo edit summary |
||
| Line 28: | Line 28: | ||
* Support windowless compositor | * Support windowless compositor | ||
** Make window property optional in WaylandOutput? | ** Make window property optional in WaylandOutput? | ||
* Rename QML import from QtWayland.Compositor to QtWaylandCompositor? | |||
* Move extensions to QML modules? e.g. import QtWaylandCompositor.XdgShell 1.0 | * Move extensions to QML modules? e.g. import QtWaylandCompositor.XdgShell 1.0 | ||
* Support multiple client buffer integrations simultaneously | * Support multiple client buffer integrations simultaneously | ||
Latest revision as of 08:51, 8 June 2018
Back to Qt contributors summit 2018 Program
General
- Deprecating old shells (xdg-shell v5, wl-shell, eventually xdg-shell v6)
- Subsurfaces
Client
- Making APIs public?
- Solving the backing store flickering problem (mostly on gnome-shell).
- QtBase popup model (tree) doesn't match xdg-shell (linear stack)
- Window decorations
- Improving looks
- Supporting server-side decorations
- Avoid unnecessary deletions of wl_surface/xdg_surface? (attaching null buffers)
Compositor
- Towards Qt 6
- Use pointer handlers?
- Remove sizeFollowsSurface
- Change defaults:
- autoCreatePopupItems: true
- sizeFollowsWindow: true
- windowSystemCursorEnabled: nested ???
- Make APIs for different shells source compatible (duck typing)?
- Support windowless compositor
- Make window property optional in WaylandOutput?
- Rename QML import from QtWayland.Compositor to QtWaylandCompositor?
- Move extensions to QML modules? e.g. import QtWaylandCompositor.XdgShell 1.0
- Support multiple client buffer integrations simultaneously