lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

64
active users

#gtk

4 posts4 participants0 posts today

Greetings Programs!! We're back at it starting a brand new cycle towards @pidgin 3.0 Experimental 4!! When are the experimental versions over? Once we've stabilized a whole lot more API and that doesn't happen without putting in the work which is what we're doing tonight! Come on by!!

twitch.tv/rw_grim
youtube.com/@rw_grim

Twitchrw_grim - TwitchMaking Pidgin The Universal Chat Client on Twitch! | C/GTK
Continued thread

Happy Disability Pride Month everybody :)

During the past few weeks, there's been an overwhelming amount of progress with accessibility on GNOME Calendar:

Event widgets/popovers will convey to screen readers that they are toggle buttons. They will also convey of their states (whether they're pressed or not) and that they have a popover.

Calendar rows will convey to screen readers that they are check boxes, along with their states (whether they're checked or not). Additionally, they will no longer require a second press of a tab to get to the next row; one tab will be sufficient.

Month and year spin buttons are now capable of being interacted with using arrow up/down buttons. They will also convey to screen readers that they are spin buttons, along with their properties (current, minimum, and maximum values). The month spin button will also wrap, where going back a month from January will jump to December, and going to the next month from December will jump to January.

Events in the agenda view will convey to screen readers of their respective titles and descriptions.

Accessibility on Calendar has progressed to the point where I believe it's safe to say that, as of GNOME 49, Calendar will be usable exclusively with a keyboard, without significant usability friction!

There's still a lot of work to be done in regards to screen readers, for example conveying time appropriately and event descriptions. But really, just 6 months ago, we went from having absolutely no idea where to even begin with accessibility in Calendar — which has been an ongoing issue for literally a decade — to having something workable exclusively with a keyboard and screen reader! :3

Huge thanks to @nekohayo for coordinating the accessibility initiative, especially with keeping the accessibility meta issue updated; Georges Stavracas for single-handedly maintaining GNOME Calendar and reviewing all my merge requests; and @tyrylu for sharing feedback in regards to usability.

All my work so far has been unpaid and voluntary; hundreds of hours were put into developing and testing all the accessibility-related merge requests. I would really appreciate if you could spare a little bit of money to support my work, thank you 🩷

ko-fi.com/theevilskeleton
github.com/sponsors/TheEvilSke

GitLabImprove accessibility of GcalEventWidget (!587) · Merge requests · GNOME / gnome-calendar · GitLabCalendar application for GNOME

I did a thing. while working on native NFC capabilities, i ended up writing a test program which reads all the info from EMV cards (such as Visa/Master/Amex) and dumps it to try and learn the payload.

the info shown in the #GTK interface is fairly basic mostly as demo, but it dumps a lot more to the shell:
github.com/FakeShell/nfc-teste

it may be possible to use this for malicious purposes with the right skill set, so please use it responsibly =)

sysctlview freshports.org/deskutils/sysct is a GUI utility for sysctl on #FreeBSD. :freebsd:
It's probably my first #opensource project 👨‍💻 , it's still in the Ports Collection 📦 and runs fine, but it hasn't been updated in years.

Maybe it's finally time to brush up on #C++ and give sysctlview a proper rewrite.
The original version uses #gtkmm (#GTK for C++), but a few years ago I ran a poll and most people preferred #qt
So maybe a QTsysctlview is on the horizon? 👀

🎉 Filmbook is now available on Flathub! 📷

Your film tracking app just got easier to install! You can now get Filmbook directly from Flathub:
https://flathub.org/apps/page.codeberg.bjawebos.Filmbook

Built with Rust & GTK4/libadwaita, Filmbook helps analog photographers keep track of their film usage with a smooth, modern interface that works great on desktop Linux and even Linux phones like the Librem 5 and Pinephone Pro!

Calling all analog photographers: I need your creative input! What features are you missing? What would make your film photography workflow even smoother? Your ideas will help shape the future of Filmbook.

Share your thoughts and join our community:
https://codeberg.org/bjawebos/filmbook

#filmphotography #analogphotography #flathub #linux #opensource #rustlang #gtk #filmbook #community #librem5 #pinephone

Calling all analog film photographers! 🎞️ I've been working on Filmbook, an open-source app to help you keep track of your film usage. It's built with Rust & GTK4/libadwaita for a smooth & modern experience – and it even runs on Linux phones like the Librem 5 and Pinephone Pro! 📱

The first version is ready for testing, and I'd love your input on what features would make it even better! Join the community & help shape Filmbook:
https://codeberg.org/bjawebos/filmbook ✨ #filmphotography #analogphotography #rustlang #gtk #opensource #community #testing #featureideas #librem5 #pinephone #linuxphone

Yesterday the "Reflection" project started officially as part of the new @PrototypeFund round! 🌟🌈

The team consists of @p2panda and people from the GNOME gang around @tbernard and @jsparber.

We gonna release "Reflection" (formerly Aardvark) - a GTK-based, collaborative, local-first text editor! Aaaand:

All of this is part of a larger effort to explore p2p code, UX patterns, reusable UI components, debugging tools, organize events and document our learnings.

Replied in thread

My problem was: the font in #GTK 4 apps (Firefox, #Gnome etc.) was suddenly unreadably large, while in GTK 3 apps (and KDE, and all others) it was the usual size.

Apparently the core of my problem was: some dpi setting in #Xorg defaults to 96 dpi; and even though xrandr showed the correct physical screen dimensions at 130 dpi, the output of xdpyinfo stayed at 96 dpi.

`xrandr --dpi 130` did the trick.

(Don't @ me about wayland. You don't understand my use case, and I will block you.)

Seems my (not so) small new feature PR for #Lutris will actually happen (well, at least the PR - let's hope they accept it). Works rather fine by now. :blahaj:
Should help make game installers more resilient having more than one file source. Also the revamped file handling should allow for easier addition of new file sources in the future.
Have to do some cleanup before submitting it though.
#coding #Python #GTK #gaming

Would any #windows #developer want to work on a funky #Gtk C++ bug?

The Inkscape project is empty of windows developers and needs some help fixing a fairly serious issue: gitlab.com/inkscape/inkscape/-

If I had a windows machine, I'd have tried to fix this one. But I'm completely at sea for this type of issue without the OS on hand. (don't try developing on a VM or old computer, Inkscape is too big and slow to build on windows for that)

GitLabWindows: Inkscape switches back and forth between two files with grids if Document Properties open (#5219) · Issues · Inkscape / inkscape · GitLab Summary: If I have multiple Inkscape windows open and I try to open the Document Properties dialog, it either doesn't open...