From 494fb26f9e6d3f44cdce56faceaaec4fe0c5eb76 Mon Sep 17 00:00:00 2001 From: "Pedro M. de Echanove Pasquin" Date: Wed, 23 Sep 2026 20:55:07 +0200 Subject: [PATCH] README: ltk is not mobile-first, its surfaces adapt to any screen Two lines carried the mobile-first framing that Eydos is dropping across its components. "mobile-first Linux shells" appeared among the cases the toolkit is especially relevant for, and "attention to mobile power usage" among the priorities its origin explains. Neither describes what ltk does. There is no mobile edition and no desktop edition of anything built with it: the same widgets are designed to work at any size and with any input, touch or pointer, and the layout is chosen per screen at run time. A reader who takes "mobile-first" at face value concludes that a desktop application is a secondary use of the toolkit, which is the opposite of the intent. The same framing is being dropped from forge and crustace. The power usage line is imprecise for a second reason. What makes a toolkit care about wakeups, redraws and idle cost is that the device runs on a battery, not that it is a phone: a laptop has the same constraint and a board on mains power has neither. "attention to power usage on battery-powered devices" states what the priority is actually about and still covers the phones it was written for. Documentation only. No code and no public API is touched, and these were the only two occurrences of the word in the file. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 82de714..904db49 100644 --- a/README.md +++ b/README.md @@ -73,7 +73,7 @@ model is "public Wayland toolkit with production consumers" rather than This makes it especially relevant for: - Wayland applications -- mobile-first Linux shells +- Linux shells that adapt to any screen, from phones to desktops - launchers and dashboards - greeters and lock screens - compositor-side or embedded UI surfaces @@ -370,7 +370,7 @@ That origin matters because it explains the current priorities: - strong Wayland focus - support for layer-shell and shell-style overlays -- attention to mobile power usage +- attention to power usage on battery-powered devices - theming and runtime surfaces that fit an operating system environment ## License