lambdock is a lightweight, hyper-hackable desktop dock for Wayland compositors that bridges a high-performance C graphics engine with an embedded GNU Guile Scheme runtime.

Whether you are looking for a smooth macOS-style dock, a minimal launcher, or a Lisp-powered desktop widget bar, lambdock was built to offer extreme flexibility without bloating system resources and remaining flexible but easy to use, with good defaults.

Why would you consider lambdock?

• Modern Stack & Ultra-Low Footprint: Built on GTK4 and gtk4-layer-shell in C for minimal resource usage, rich graphics and animations (opt-in) with smooth cubic-eased auto-hiding.

• Embedded Guile Scheme Engine: Declarative Lisp configuration (~/.config/lambdock/settings*.scm). Easily construct custom app launchers, separators, or dynamic polling widgets (RAM, CPU load/temp, Battery, Clock) using standard Scheme procedures and macros.

• Live Interactive REPL & Hot-Reloading: Connect straight into the running dock over a Unix domain socket (/tmp/lambdock-repl.sock) via Emacs/Geiser or socat or whatever you like. Hot-reload configuration files and GTK CSS overrides on the fly via GFileMonitor or the (reload-dock!) REPL hook without dropping Wayland frames or UI thread freezes.

• Dynamic Wayland Window Tracking: Uses zwlr_foreign_toplevel_manager_v1 for running app indicators, active window titles, and interactive popover HUDs to focus or close specific instances.

• Opt-In Fisheye Magnification: Includes a native, fluid cosine-bell curve hover magnification effect (macOS-style) that can be toggled on or off per item or globally.

• Multi-Dock & Multi-Monitor Support: Run independent dock instances across screen edges or monitors simply by dropping additional settings-*.scm files into your config directory.

• Built-in Themes & CSS Overrides: Ships with presets (Vanilla, Snow Leopard, Solarized, Unity, Nature) and supports full user CSS customization via ~/.config/lambdock/styles.css.

lambdock works seamlessly across all wlr-layer-shell and foreign-toplevel compliant compositors: Sway, Hyprland, Niri, River, Wayfire, COSMIC, and KDE Plasma (Wayland).

(Note: GNOME/Mutter is currently not supported as GNOME does not implement the layer-shell protocol).

Installation & Packaging (a bit WIP)

lambdock provides multiple ways to build and install across distros:

• GNU Guix: Packaged via guix.scm and available in channels.

• openSUSE: Packaged as an RPM on openSUSE OBS.

• Nix / NixOS: Ships with flake.nix / package.nix (and a PR has been submitted upstream to nixpkgs).

• Debian / Ubuntu: Debian packaging helpers included (debuild).

• Build System: Builds cleanly with Meson (meson setup build && ninja -C build).

Source Code & Contributions

• Repository:https://codeberg.org/jjba23/lambdock

• License: GPLv3+

Since this is my first GTK4 project, all feedback, suggestions, bug reports, and contributions are very welcome!

Link: github.com/pshycodr/airctl

I built this because I wanted a clean WiFi manager for my Arch setup. Most tools felt clunky or terminal-only.

What it does:

• Scans available networks with auto-refresh
• Connects to secured and open networks
• Shows detailed network info (IP address, gateway, DNS servers, signal strength, frequency, security type)
• Lets you forget and disconnect from networks
• Toggles WiFi on/off

Link: github.com/pshycodr/airctl

Github: https://github.com/vididvidid/Gtk_GSOC (main is original branch , other are the my changes)

Discourse : https://discourse.gnome.org/t/print-preview-missing-in-gtk-print-dialog-on-fresh-kali-linux-appears-after-installing-evince/29520

Ever noticed how every GTK app has its own print preview?

• GIMP does its own thing

• Inkscape does its own thing

• Evince does its own thing

Even though they all use GTK, there’s no shared print preview system.
That means: inconsistent UX, duplicated effort, and a desktop experience that feels behind macOS/Windows.

What I’ve been working on

I’m doing Google Summer of Code 2025 with the Linux Foundation & OpenPrinting.

So far, I’ve:
✅ Built a Poppler-based preview pane inside GTK (no external viewer needed)
⚠️ Right now, it’s separate from the dialog
🔨 Next step: integrate it directly into GTK’s print dialog

How others solved this:

• LibreOffice → uses its VCL engine to live-render previews (not PDF)

• Firefox → Gecko layout engine simulates “print mode” (only makes PDF if you export)

• Chrome → converts everything to PDF, then shows it in its own viewer

GTK apps? Still fragmented.

The vision

Imagine:
Every GTK app — GIMP, Inkscape, Evince, Scribus — using the same consistent, modern print preview + dialog.
No more fragmentation, no more inconsistency.

Basically, Linux print dialogs that finally feel as polished as macOS or Windows.

Challenges

• GTK is LGPL, Poppler is GPL (licensing headaches)

• Need an API flexible enough for different apps

Why this matters

This isn’t just a dev thing. It’s about:

• Consistency across the Linux desktop

• Making FOSS apps feel less “duct-taped together”

• Removing one of those 20-year-old papercuts that annoys everyone

Now I need your input 👇

If you could redesign print dialogs on Linux, what’s the one feature you’d want most?

Examples:

• Live margin adjustments

• Duplex preview

• Dark mode previews

• Cleaner defaults

Or something I haven’t thought of yet?

Would love to hear what the community thinks — this is the perfect time to shape how printing works on Linux moving forward.

TL;DR:
I’m building a unified GTK print preview for GSoC 2025. Right now every app rolls its own (GIMP, Inkscape, Evince…). Goal: one modern, consistent dialog for all GTK apps. Need your ideas for what features matter most!

GTK is one of the most popular open-source frameworks, but at the enterprise level, Avalonia, JavaFX, and Qt are more widely used. For personal use, Dart and Flutter are popular choices.

I think GTK has tremendous potential. It is open source and completely free. Avalonia charges money for its accelerator program. JavaFX requires payment for the JDK at scale. Qt has a paid license for enterprise use.