Accéder au contenu principal

Have You Played Atari Today? đŸŽ”

This is a guest article by Laurent « Hell PĂ© » Pointecouteau, the Alfred Pennyworth of GNOME Games who relentlessly works in the shadows to help make Games what it is, when he’s not busy writing in French about video games or slacking on Twitter.

I used to be really excited at New Stable Release Blog Posts™ like this one, back in the day when you had to wait six months for getting new GNOME stable releases (and matching Ubuntu PPAs) in order to discover what was new in your favourite apps. But nowadays, these blog posts, while still a delight to read, are just a little less surprising than before, and we’ve got Flatpak to thank for that!

So, here’s a quick reminder: Games can be obtained by two ways. The old-school way, with the version provided by your distro; and soon, hopefully, your distro will upgrade to the brand-new 3.26 stable version that we’ve just released. And the Flatpak way, the one we actually recommend if your system is ready for it: it’ll give you the choice between the 3.26 version — packed with our hand-picked selection of emulation cores! — and the Unstable Nightly version, where you can test (at your own risk as usual) all of the good stuff Adrien and folks have been working on during all this time.

So, either you already had a taste of all the new stuff in Games 3.26 and just need a recap, or you’re only using the stable version and want to know what’s new in store: in both cases, this New Stable Release Blog Post™ is for you!

  • You can now just double-click your ROM files in Files (or any file manager), and it will automatically be launched in Games, just like your music or video files already behave. That’s because Game URIs can now be passed as command line arguments. Launching a game this way will make it appear permanently into your games library ; you can also add it manually using the new "Add game files" button.
  • You can also setup a custom gamepad configuration, if the default one does not suit you, using a new wizard in the Preferences page. Many thanks to Abhinav Singh, who did a wonderful job on this as its Google Summer of Code project, on which you can learn more on Singh’s personal blog here :
  • We’ve brought up some visual tweaks to make Games better integrate with your desktop themes, alongside Flatpak improvements that already help make Games look better. You will probably notice them if you’re using a different GTK theme than the default Adwaita one.
  • For those of you using the Flatpak version of Games, you may now enjoy your Atari 2600, Game Boy Advance, WonderSwan and WonderSwan Color games with 3.26, fully integrated as usual! We’ve also begun to list the Atari Lynx and MS-DOS games you may have on your computer, but they cannot be launched yet.
  • And finally, a lot of code was rewritten and revamped to improve game detection (especially for PlayStation games), gamepad handling, the retro-gtk plugin infrastructure and more.

So that’s what in store for you with Games version 3.26! What’s next, you may ask?

  • More cores! No true ludothĂšque can be taken seriously without some Sega games, and we may be able to bring you state-of-the-art Mega Drive/Genesis and Mark III/Master System emulation very soon.
  • Since the first release of Games, we’re pulling our cover arts from, which is a nice open database but not always very accurate. While looking for an alternate solution, we’ve discovered the very promising Screenscraper project, already used on the well-known Raspberry Pi-focused distributions, Recalbox and Retropie. So, we are considering migrating to Screenscraper for all our database needs at some point in the future, not without the help of the Grilo team of course (shoutout to our trusty friend Bastien Nocera 😉)
  • Some even bigger code refactoring is in order, with Adrien tirelessly working on porting retro-gtk from Vala to C. You’ll soon learn everything about it in a future blog post.
  • We’ve got a couple of high-priority bugs that we really want to squash out for the next release, especially the one that prevent Linux (including Steam) games from being launched from the Flatpak version of Games. Of course, any help on this would be very much appreciated!
  • And of course, we’ve got a lot of projects for Games: to get a good glimpse, go check out our ever-growing Roadmap.

So now, you know how it works: you can enjoy the latest release of Games by directly downloading and launching the flatpakref file provided on our GNOME Wiki page, or you can give the Unstable Nightly version (again, at your own risk) a try — or you can do both, since it’s all safely sandboxed by Flatpak of course.


  1. Why are you porting from Vala to C?

    How long is taking that process of conversion?

    1. I'll detail all of that in the next article so I recommend to save your questions for that one. But to sum things up:
      - retro-gtk does too many low-level memory management and has to interface too much with C for Vala to be a good choice: too much of the code was there to expose the C parts in Vala,
      - it wouldn't be too long for an application, but porting a library exposing a VAPI is very tricky, an hence, long.


Enregistrer un commentaire

Posts les plus consultés de ce blog

Librem 5 ❤️ GNOME 3.32

I am glad to announce that the tooling I am working on since the beginning of the year is ready to be used!Thanks to new features introduced into libhandy 0.0.3 and 0.0.4 and thanks to a few fixes to Adwaita in GTK+ 3.24.1, you can make GTK+ 3 apps adaptive to work both on the desktop and on the upcoming GNOME-based Librem 5 phone.We are early in the GNOME 3.32 release schedule and the Librem 5 will be released a bit after it, so if you want your apps to work on the Librem 5, now is the best time: use libhandy 0.0.4 and up, use GTK+ 3.24.1 and up and target GNOME 3.32! A few apps like Fractal, Podcasts, Calls and Chatty are already using libhandy's adaptive capabilities, and other apps are working on their adaptive transition like Contacts, Games, Geary and Settings (all are works in progress). libhandy is available in Debian Unstable and Arch's AUR repository, and I wish it would be in Fedora already to let GNOME Settings' CI pass.For the moment, libhandy is a GTK+ 3 widg…

One Widget to Adapt Them All and to The Librem 5 Port Them

In my previous article I shared my plans to help porting existing GTK+ applications to Purism's upcoming Librem 5 phone without having to fork them. This article will present the GTK+ widget I developed for Purism to make this happen.For more information on what Purism is working on for the Librem 5, please check Nicole Faerber's latest article.C'est pas sorcierThe underlying idea is to allow applications to dynamically switch between the two main GNOME application layouts: a row of panels — each panel being the view of an element from the previous one — and a stack of panels. The goal isn't to changes applications using the stack paradigm but the ones using the row one, allowing them to reach smaller sizes and to be usable on constrained sizes while keeping their initial paradigm and design when the screen space is sufficient. The development cost to port the applications to this adaptive design should be as low as possible.To achieve that, I wrote a GTK+ widget which…

Adaptive GNOME Web

I started working on making GNOME Web work well on the Librem 5; to be sure it fits a phone's screen I want the windows to fit in a 360 points width, which is definitely small. To do so I started with the advices from Tobias Bernard to make Web have two modes that I named normal and narrow. The normal mode is Web as you know it, while the narrow mode moves all buttons from the header bar but the hamburger menu to a new action bar at the bottom, letting the windows reach yet unreachable widths. Web autmatically adapting to small sizes. And now, with device rotation on a tablet. The code is overall ready, I still need to break it into reviewable bits before submitting it upstream.Once this get merged:we want to not show tabs in narrow mode and instead to display a popover listing the available pages,we want to make the search bar shrink rather than to limit the minimum window size,we consider migrating away from the application menu model.A quick layout test of the pages popover. P.S.…