Search

Items tagged with: Libadwaita


Being a mod on /r/gnome reddit can be pretty entertaining. I have this person who was unhappy that a #gtk3 converted to a #libadwaita app. When I told him that software freedom is you have the ability to fork and maintain the gtk3 version yourself this is the response:

'''so software freedom is the freedom of developers to sneak into my house, paint the walls a different colour and move my furniture about however they like without warning?'''

Uh, yeah. K.

#gnome #linux #OpenSource


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…

#Accessibility #a11y #DisabilityPrideMonth #GNOME #GNOMECalendar #GTK #GTK4 #Libadwaita #FreeSoftware #FOSS #OpenSource


As part of our volunteer-driven accessibility initiative in GNOME Calendar, and for the first time in the 10+ years of Calendar's existence, we finally completed and merged the first step needed to have a working calendar app for people who rely on keyboard navigation. This merge request in particular makes the event widgets focusable with navigation keys (arrow left/up/right/down) and activatable with space/enter. This will be available in GNOME 49.

Most of GNOME Calendar's layout and widgets consist of custom widgets and complex calculations, both independently and according to other factors (window size, height and width of each cell, number of events, positioning, etc.), so these widgets need to be minimal to have as little overhead as possible. This means that these widgets also need to have the necessary accessibility features reimplemented or even rethought, including and starting with the event widgets.

We also hope to get other parts of GNOME Calendar accessible before GNOME 49, but I can't promise anything at the moment. We did start working with making the month view accessible: gitlab.gnome.org/GNOME/gnome-c…

#GNOME #Calendar #GNOMECalendar #GTK4 #GTK #Libadwaita #Accessibility #a11y #Linux


Discovered that #libadwaita apps can enable the convenience "What's New" button in their About dialog to show release notes: gnome.pages.gitlab.gnome.org/l…

Some #GNOME apps already use it: stable releases of Calendar, Shortwave, Showtime, Papers, System Monitor, Decibels, Warp, etc.

I've now filed RFEs for this in Tuba, Epiphany, Contacts, Fractal, Secrets, Warehouse, Maps, Apostrophe, Snapshot, File Roller, etc.

Ideally I'd want to suggest it in Ptyxis, Text Editor, Builder, Loupe & Pika…


Last week Exercise Timer by Lőrinc Serfőző was accepted into Circle! It's a cute little app to create timers for high-intensity interval training 🏋️⏲️

apps.gnome.org/Hiit

#gnome #circle #libadwaita


Introducing Refine, an app to tweak advanced and experimental settings in GNOME. It is an alternative to GNOME Tweaks, and is a pet project I'm currently working to experiment with PyGObject and dconf, while following the data-driven, object-oriented, and composition paradigms.

The entire codebase is made up of widgets that provide all the functionality needed to add an option. For example, instead of adding each option programmatically in Refine, the ultimate goal is to have it all done in the UI file.

For example, if we want to add an option to enable or disable middle click paste, all we need is the following code in the UI file:

$RefineSwitchRow {<br>  title: _('Middle Click Paste');<br>  schema-id: 'org.gnome.desktop.interface';<br>  key: 'gtk-enable-primary-paste';<br>}<br>

That's it. The RefineSwitchRow widget will do whatever it needs to do to ensure the option is available, grab the setting if it's available, and display it to the user. Many of these widgets provide extra functionality, such as a Reset button.

You can get Refine on Flathub: flathub.org/apps/page.tesk.Ref…

Everything else (source code, screenshot, etc.) is in the project website: tesk.page/refine/, as well as the Flathub link.

#GNOME #Flatpak #Flathub #FOSS #OpenSource #GTK #Libadwaita




A new release of #Multiplex, the app that lets you watch torrents together in a way similar to Apple's SharePlay and Amazon's Prime Video Watch Party, is out!

This brings the latest and greatest #GNOME and #libadwaita technologies, modernizes the underlying dependencies, enhances accessibility, and makes it easier to contribute to the project with improved contributor documentation and a rewrite of the UI markup!

And more is to come soon-ish, so stay tuned 🥳



I have released a new version of Exhibit!
- Improved settings with four default configurations for different file types and the possibility to save custom ones
- Bundled four HDRI by default, but more can be added
- Added a button to open the file in an external app
- Automatic reload on file change
- More ways to color models
- Improved point cloud support
- Updated F3D to latest version

Get it on #Flathub: flathub.org/apps/io.github.nok…

#GNOME #GTK #Libadwaita



Over the last months, we've completely redesigned and rewritten @dino 's accounts and settings dialogs. The dialogs are combined into a single one now, which is adaptive and offers additional features like an option for OMEMO by default. The rewrite also resolves a number of issues and feature requests that were raised with the old implementation. It's still work in progress and will require further polishing.

#dino #xmpp #gtk #libadwaita




I think I might have found a way to run and distribute #GTK4/ #libadwaita apps (without Broadway) locally on an Android device 👀




#Tuba v0.7.0 is now available, with many new features and bug fixes!

✨ Highlights:
- Filter handling and editing
- User and Post reporting
- AdwDialogs (thanks oscfdezdz@mstdn.social)
- Tracking parameter stripping on paste (thanks kop316@fosstodon.org)
- 1:1 character counting with Mastodon
- Syntax highlighting
🧵

As always, there are too many changes to list here, if you're more interested, check out the full release changelog:
github.com/GeopJr/Tuba/release…

#GTK #GNOME #Vala #libadwaita #mastodev






Workbench 45.4 is out 🛠️

flathub.org/apps/re.sonny.Work…

• Restore on-disk projects on start
• Restore scroll and cursor positions on format and Run
• Add "Copy" and "Select All" to Console
• Add Vala formatter support
• Add WebP image format support
• Library: Add "Context Menu" demo
• Library: Add "HTTP Server" demo
• Library: 12 demos ported to Python, 4 to Vala and 2 to Rust

Happy hacking / learning / prototyping

#Linux #development #GTK #GNOME #libadwaita #Rust #JavaScript #Python #Vala


Currently working on two #gnome apps!

- Scripter: A simple app for basic scripts ⌨️ & calculations 📐 [GitHub: github.com/david-swift/Scripte…]
- Flashcards: Create, edit, and study flashcard sets 🎓 - easily import your existing Quizlet sets [GitHub: github.com/david-swift/Flashca…]

Both are written in #swift using an interface similar to #swiftui for #gtk and #libadwaita [GitHub: github.com/AparokshaUI/Adwaita]



So I've been working with GTK4/Libadwaita in Python (in Flatpak), and I'm trying to get notifications to work.

I keep getting this error: "gi.repository.GLib.GError: g-io-error-quark: Error calling StartServiceByName for org.freedesktop.Notifications: Timeout was reached (24)"

Am I missing Flatpak overrides? (Docs seem to say no docs.flatpak.org/en/latest/por… )

Am I doing this wrong? (Code at github.com/TheKrafter/Grouping… )

#AskFedi #GTK4 #Python #LibAdwaita #gnome #Programming


Are you interested in working on GNOME, writing Rust apps, or working with Fonts? If so, you may be interested in taking a look at gitlab.gnome.org/GNOME/gnome-f… :)

This port may take a while, and I greatly appreciate any help available. I've laid out a list of tasks to be done before merging, and if anyone wants to take something on let me know and we can work together.

If you want to help with the effort, please join #fonts:gnome.org on Matrix :) (matrix.to/#/#fonts:gnome.org)

(boosts appreciated)

#GNOME #Rust #Fonts #gtk-rs #gtk4 #libadwaita


it's been some time since the last Muzika update, but I (and some people that joined along the way) didn't stop working on it.

A few changes:

1. Column view for playlists & albums on larger screens

2. Decent (not perfect) mobile support

3. All links are now underlined for better visibility/a11y

4. Simplified code & improved perf (not yet perfect)

5. We now have flatpak builds (CI)

6. The app now supports translations

etc, etc.

see it at github.com/vixalien/muzika

#gnome #gtk #libadwaita






Using #GTK and #Libadwaita in #swift Attempt Number 2.

Instead of using GIR to generate the code, use hand-written bindings.
More work? - Yes

Full coverage? - No

Better API and easier to use? - Yes


I spent yesterday evening trying to see how to make apps that use #libadwaita (the latest UI for #GNOME), and walked away with a streak of anger over a surprising lack of documentation and examples.

#GTK and #GNOME app development have always been a quest that involves throwing a ring in a fiery mountain, while hoping for the best, but in the 25 years since GTK+'s introduction, it has only gotten worse, it just looks prettier now. sigh. #linux


Sometimes I find it very hard to know how to look for/describe #GNOME bugs. I could use some help with this one. It's a bug in #libadwaita as I can trigger it both in GNOME Files and GNOME Settings. I just have no clue how to describe it. I think searching on "dialog" might be too narrow of a search, and I also don't know what to give as extra info (platform, version...). I can't seem to find it in the gitlab repo, which surprises me as it's such a major regression...

#gtk #adwaita