Skip to content
HomeVideos
AllLongsCategoriesPlaylists
BooksBlogsPodcasts
HistoryListsWatch laterLiked videosFollowing

The videos, books, blogs and podcasts Hacker News keeps recommending, all in one place.

VideosBooksBlogsPodcastsAboutPrivacySettings

Data from Hacker News, HackerTube, HackerBooks, HackerBlogs and Open Library. Credits · Not affiliated with Y Combinator.

HomeVideosBooksBlogsPodcasts
Ctrl K

    Qt 5 based 3D Wayland compositor

    Samuel Rødal

    4 HN mentions · mentioned in 4 months, 2013–2020

    YouTube

    2:26 · 133K views · Sep 16, 2012

    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.

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

    Systems, Networks & SecurityLinux & open-source ecosystemsComputer graphics & renderingEmbedded systems & DIY electronics
    1. 45:35
      The Real Story Behind Wayland and X - Daniel Stone (linux.conf.au 2013)Mladen Mijatov104K views • 13 years ago
    2. 45:35
      [Linux.conf.au 2013] - The real story behind Wayland and XHackersOnBoard35K views • 13 years ago
    3. 45:35
      The real story behind Wayland and XLinux.conf.au 2013 -- Canberra, Australia46K views • 11 years ago
    4. 42:20
      Writing a Wayland Compositor in Zig - Isaac FreundZig SHOWTIME26K views • 6 years ago
    5. 7:42:30
      XDC 2020 - Day 1 - September 16, 2020X.Org Foundation24K views • 6 years ago
    6. 46:06
      Gtk to Qt - a strange journey [linux.conf.au 2014]Konstantin Bläsi46K views • 12 years ago
    7. 29:16
      SYMBOLICS S-PACKAGES 3D GRAPHICS AND ANIMATION DEMORed Martian14K views • 13 years ago
    8. 18:50
      Creating a Doom-style 3D engine in CBisqwit991K views • 11 years ago
    9. 5:05
      New Voxel Engine Reveal - Crystal Islands ExperimentJohn Lin394K views • 5 years ago
    10. 1:10:00
      A Deep Dive into Nanite Virtualized GeometrySIGGRAPH Advances in Real-Time Rendering279K views • 5 years ago
    11. 2:13
      Brigade 3.0 preview - Real-time path tracingicelaglace439K views • 12 years ago
    12. 3:36
      elevated by Rgba & TBC | 4k intro (FullHD 1080p demoscene demo)Demoscene High-Quality Videos (Annikras)317K views • 15 years ago
    13. 6:52
      Brigade 3 real-time path tracingSam Lapere (Supergastrocnemius)89K views • 13 years ago
    14. 5:25
      Make Your Renders Unnecessarily Complicatedsirrandalot1.2M views • 3 years ago
    15. 13:09
      Raycasting engine in Factorio (vanilla 0.17) - Facto-RayO v1.0arrow in my gluteus maximus1M views • 7 years ago
    16. 42:00
      I painted a Landscape with MathematicsInigo Quilez812K views • 4 years ago
    17. 2:42
      ubuntu 3D Desktop (Cube) (KDE & Compiz Fusion & CairoDock) fullHD 1080pPhilip J. Bugsington614K views • 16 years ago
    18. 16:43
      Blender 3.0 Beginner Tutorial - Part 1Blender Guru9.3M views • 4 years ago
    19. 15:39
      ShaderToy LiveCoding - The Drive Home - 1. Basic SetupThe Art of Code28K views • 8 years ago
    20. 23:38
      Interactive notebooks ~ Pluto.jl | Fons van der Plas | JuliaCon 2020The Julia Programming Language48K views • 6 years ago

    4 comments from Hacker News

    1. @bachbackOct 2013· in “NodeOS”

      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 this video the future is going to be cool ;)

      CitesView on HN
    2. @mitchtbaumOct 2018· in “The case for pair programming”

      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 this video so, hopefully more people will start focusing on [LINK] and other Rust desktop/handheld application level development.

      CitesView on HN
    3. @drivebyacct2May 2013· in “Meta: The Most Advanced Augmented Reality Interface”

      Skip X, jump to QML and QWayland. this video Take that and extrapolate. Doesn't seem that "crazy" really. Compiz and KWin both already have window animations you're describing. There was even a Wii-head-tracking plugin for compiz that would give your desktop a third perspective dimension. (Moving your head would reveal the edges/bits of the other windows underneath higher ones). It'd be a neat demo, but it sounds like a nightmare for daily usability, etc.

      CitesView on HN
    4. @vetinariAug 2020· in “GTK 3.99”

      With wayland, you can do this and the apps won't notice because of the limits placed upon them earlier: this 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?

      CitesView on HN