mastodon.world is one of the many independent Mastodon servers you can use to participate in the fediverse.
Generic Mastodon server for anyone to use.

Server stats:

8.1K
active users

#gtk

10 posts10 participants2 posts today

Ra mắt thư viện Rust mã nguồn mở đầu tiên cho GTK: RustEditorKit! 🚀 Cung cấp nền tảng vững chắc để xây dựng các thành phần chỉnh sửa, tập trung vào hiệu suất và kiến trúc rõ ràng. Mong nhận được sự đóng góp từ cộng đồng!
#rust #gtk #opensource #thuvien #laptrinh #rustlang #opensourceproject

reddit.com/r/SideProject/comme

LuaGObject, my LGI fork, is now available. It dynamically generates Lua bindings to GObject libraries like Gtk. Since the last release of LGI, LuaGObject now also:

- Supports Gtk4 and Adwaita
- Works on Lua 5.4 and 5.5
- Builds using Meson
- Has extra quality-of-life features

Learn more ⇒ vtrlx.ca/posts/2025/luagobject
Source code ⇒ github.com/vtrlx/LuaGObject
Install from LuaRocks ⇒ luarocks.org/modules/vtrlx/lua

www.vtrlx.caIntroducing LuaGObjectVersion 0.10.0 is now available.
#Lua#GNOME#Gtk
Continued thread

And today at 10:10 AM Brescia time I'm going to be speaking about #GTK widget layout things.

Ever ran into "gtk_widget_measure: assertion 'for_size >= -1' failed"? Yeah, those layout things.

I had some less time to prepare compared to yesterday's talk (procrastination got the best of me); let's see whether I can still manage it 😅

Continued thread

After two weeks of writing, revising, and trying to make everything as digestible as possible, I finally published "GNOME Calendar: A New Era of Accessibility Achieved in 90 Days", where I explain in detail the steps we took to turn GNOME Calendar from an app that was literally unusable with a keyboard and screen reader to an app that is (finally) accessible to keyboard and screen reader users as of GNOME 49!

tesk.page/2025/07/25/gnome-cal

TheEvilSkeleton · GNOME Calendar: A New Era of Accessibility Achieved in 90 DaysThere is no calendaring app that I love more than GNOME Calendar. The design is slick, it works extremely well, it is touchpad friendly, and best of all, the community around it is just full of wonderful developers, designers, and contributors worth collaborating with, especially with the recent community growth and engagement over the past few years. Georges Stavracas and Jeff Fortin Tam are some of the best maintainers I have ever worked with, especially Jeff’s underappreciated superhuman capabilities to voluntarily coordinate huge initiatives and issue trackers. One of many Jeff’s initiatives is gnome-calendar#1036: the accessibility initiative. It is a big and detailed list of issues related to accessibility, and regularly gets updated. The upcoming release of GNOME, 49, will feature the biggest update GNOME Calendar has ever received (excluding the initial release). It will also be the accessibility update, where we managed to turn GNOME Calendar from an app that was literally unusable with a keyboard and assistive technology, to an app that is actually functional with a keyboard and screen reader in about three months. This article will explain in details about the fundamental issues that held back accessibility in GNOME Calendar since the very beginning of its existence, the progress we have made with accessibility as well as our thought process in achieving it, and the now and future of accessibility in GNOME Calendar.

One of the dumbest design decisions of #GTK is to have "warp scrolling" the default primary mouse button behavior.

Previously, if you middle-clicked the scrollbar, it would jump to that position within the buffer. Primary click moved up/down by page. GTK 3 reversed this for no reason.

There are some limited scenarios where jump scrolling is desired, but you should never break a standard UX convention without a tremendous benefit. There wasn't one.

The new modal dialogs in GTK/gnome that are nailed to the parent window's center and can't be moved are such unintelligent design. Libreoffice now uses these for the paragraph style editing dialog so now you can't move the dialog anymore to look at the effect of your settings on the actual document. A similar issue happens with the "save as" dialog in many GTK applications. Often you'd want to look at the content of the document to decide on a file name.

¡Vaya sorpresa me he llevado! La interfaz #GTK de #Audacious por fin se sincroniza con el tema oscuro de #GNOME, si bien, al no ser #GTK4, no coge el color de acento.

Ojalá algún día Audacious logre migrar a GTK4, aunque al menos esta adaptación por parte de GTK3 me es suficiente para volver a darle una nueva oportunidad.