HackerTube.dev

Qt 5 based 3D Wayland compositor

Samuel Rødal · 133.1K views · 2012-09-16 · 2:26

Open on YouTube ↗

If playback is restricted in your region, try opening the original video. Use Mark watched to add it to your marked videos.

Overview

A short demo of a 3D Wayland compositor built with Qt 5 and QtWayland, mapping input to and compositing the output of Wayland applications in a 3D scene, also running on a Raspberry Pi.

On Hacker News

Cited as an existing example of 3D or spatial desktop shells and what Wayland compositing makes possible.

Discussed on HN; no positive recommendation is recorded in this export · HN mentions 2013–2020

Topics

Search by tags

What people said

vetinari · 2020-08 · Reference

With wayland, you can do this and the apps won't notice because of the limits placed upon them earlier: [VIDEO] Can macOS do it? The point of this demo is not practical usability today, but to demonstrate, that global positioning on the desktop as we know today might get much more complex in future. So why shut the door?

Read the original HN comment ↗
mitchtbaum · 2018-10 · Reference

I've been pair programming for about 6 weeks now, over Discord. The calling and screen sharing functionalities work so well that my partners and I can join and part quickly and easily. We can get deeply into what we're doing individually. But collaboratively, we can solve problems that neither of us can do alone. I like this virtual setup for multi-user interaction a lot, and hope more tools, even ones specific to virtual programming environments, come for it soon. Tuple's making a remote sharing tool that looks interesting. What comes to mind for me is a shared 3D Wayland environment, like this [VIDEO] so, hopefully more people will start focusing on [LINK] and other Rust desktop/handheld application level development.

Read the original HN comment ↗
bachback · 2013-10 · Reference

here are my thoughts. there once was chromeOS, which was the idea to build an OS as a browser. more recently exobrowser is bootstrapping chrome via node. which means you can expose rendering methods. if you compare that with what different OS layers does, you might as well use the exposed rendering methods to expose your local data and services (=KDE/Gnome). so I would study Wayland for this first. there you learn render stuff to the screen speaking to the kernel. it's 100x easier than X11. I don't know KDE/Gnome internals but I would assume with Wayland some of it can be rebuild now (?). so you could then basically script the GUI perhaps in quite new ways. if you compare that to what the exobrowser is doing you get the picture. so coreOS => Docker => wayland. network servers are booted up from remote, so the network part is becoming more core. virtualization/containers allow for different isolation of processes which speak to the network. then you have a thin layer of display. so for example imagine hookup a oculus and having that as a kind of OS, see this demo [VIDEO] the future is going to be cool ;)

Read the original HN comment ↗

Sources

Video by Samuel Rødal, played through YouTube.

Data and selection notes

HN summaries and labels may contain AI errors. HN dates refer to discussions, not video publication.

HN Library: HackerTube export (2026-10-31) and open-index/hacker-news. Upstream summaries and classifications may contain AI errors.

Views, duration and playback status refresh separately from the published catalog. When an update fails, existing data remains visible.

Selection checks
  • SaaS & AI candidates: Topic keywords do not match
  • Editor-approved picks: Editorial review is required

Rule matches identify candidates. They do not guarantee video quality or financial results.

About the library and its sources