Loupe is now GNOME’s Core app for viewing images. It’s not yet available in GNOMEOS due to a dependency issue. But everyone can help with testing by trying out the nightly builds.
This week we have landed a new design for indicating that an image is dragged over the window. Thanks to FineFindus for implementing the groundwork for this. Chris 🌱️ has tackled the task to equip Loupe with a set of help pages.
Paper Clip v3.2 is here! With a bunch of small bug fixes and improvements:
Fixed a bug in which the File Dialog would show all files instead of only PDF documents.
The app has improved its cache usage.
Document thumbnails are now scaled down using Gtk.Snapshot.append_scaled_texture, creating nicer-looking images. This can be specially noticed with PDF documents with transparent background.
Multi windows/sessions support landed in Workbench. You’ll be able to consult Library demos while working on your prototype.
This is also a requirement for future on-disk folder projects support in Workbench.
Followin up Bilal Elmoussaoui footsteps, here is a totally unnecessary screenshot of all Library demos open.
Compared to beta 2, this release features a brand new backend for reading and writing tag metadata (TagLib# -> ATL.NET). With this change, Tagger now supports a wide-range of file types and can even manage corrupted files that previous TagLib-based Tagger could not. We also added support for custom, user-defined properties that can be added to any file’s tag and we greatly improved our documentation pages available through the Help menu item.
Because the new backend is such a big change, we urge all willing users to give this beta a shot and make sure everything still works correctly :)
Here’s the full changelog:
Replaced taglib backend for tag metadata with atldotnet. This change added support for a lot more file types
Added support for the following tag properties: Composer, Description, Publisher
Added support for custom, user-defined properties
Added help documentation with yelp-tools, accessible from the Help menu action
Added more file sorting options
Improved album art design and added support for managing back cover art and exporting album art
Fixed an issue where corrupted music files would crash the app. Tagger will now display a dialog to warn the user of corrupted files
Improved UI
Updated translations (Thanks everyone on Weblate!)
Parabolic V2023.7.3-beta1 is here! In this release we improved the design of the Keyring dialog making it cleaner and more user friendly.
Behind the scenes, we upgraded to gir.core V0.4.0 which brings many improvements to using GTK and asynchronous programming in C#. As a result of this update, our code is a lot cleaner and easier to read.
However, because this is such a big change, we urge all willing users to give this beta a shot and make sure everything still works correctly :)
Here’s the full changelog:
Improved Keyring Dialog design
Updated translations (Thanks everyone on Weblate!)
Blueprint 0.10.0 is out! The biggest change is that the bind-property keyword is gone, since it was a bit confusing when to use it instead of bind. Also in this release are some improvements to the on-hover documentation. https://gitlab.gnome.org/jwestman/blueprint-compiler/-/releases/v0.10.0
GNOME Gitlab has gained two brand-new CI runners, donated by Canonical. Both are hosted at Hetzner, sporting an Intel Core i5-13500, 64GB of RAM, and 2 NVMe disks configured as RAID1 for faster disk reads.
The deployment of the new CI runners was a good opportunity to revisit our deployment automation. All runners were upgraded to the latest distribution releases, and also reworked to use podman instead of Docker, which now runs fully unprivileged for a reduced attack surface.
We have also improved the tool used to clean up the old Docker images to act more aggressively. As a result, there should be fewer issues caused by limited or no disk space.
Outside of CI/CD changes, we’re working on a replacement for Discourse e-mail integration we’re using instead of the late Mailman. Currently, it can be a little wonky as it applies Discourse permissions if the sender already has an account, causing issues with the delivery to the Board and Code of Conduct team. The new solution will be deployed shortly after GUADEC.
Speaking of GUADEC, I will be talking about short- and long-term plans for the infrastructure on Wednesday at 9:40 AMCEST. Drop by if you want to know where we’re at!
