DEV Community

Choon-Siang Lai
Choon-Siang Lai

Posted on • Originally published at kitfucoda.Medium on

Building a desktop launcher

I still use QuickSilver on my mac, despite there are multiple efforts attempting to displace it. There used to be one made for Linux, called Gnome Do, however the development eventually stopped. I settled for the built-in launcher in Gnome Shell, and then briefly moved on to rofi with this configuration.

One thing I liked a lot about Quicksilver is that I can somewhat “pipe” the result of an action to another operation, for example:


“Piping” in Quicksilver in action

For example, I can start by looking for a file DSCF8200.jpg then select an action Open With followed by selecting an application Preview. This is a flexibility that I don’t get with rofi and Gnome Shell.

Plus, I couldn’t even get rofi to run in a wayland session.

Finding a job is still looking like a long process (yes, still #OpenToWork here), just to distract my attention, I decided to start working on a simple launcher I would eventually start using. I would also take the opportunity to learn how to build a GUI application for real this time.

Considering that I am most comfortable with Python, I start with tkinter. However, I would start small and start the experiment with a CLI command. The building of the command, will serve as a blueprint for the launcher.

This is how RapidCopper started (sorry for the unimaginative name).

And yes, I am aware of the fact that tkinter GUI applications do not work in Wayland for now.

It is still in a very early stage, I am still prototyping things, and still figuring out the spec for the launcher. However, for now it does the things I want it to do.

The application still expects a setup, with

rc rebuild-index
Enter fullscreen mode Exit fullscreen mode

This sets up the configuration in $HOME/.config/rapidcopper, with a sqlite3 database as the index, and a folder for plugins.

The do subcommand is the part where it does its job. I can launch an application

rc do fire
Enter fullscreen mode Exit fullscreen mode

And it spits out a list of options

0 app: /home/jeffrey04/.local/share/applications/userapp-Firefox Developer Edition-EPEGV2.desktop - Custom definition for Firefox Developer Edition
                Firefox Developer Edition
1 app: /home/jeffrey04/.local/share/applications/firefox-developer.desktop - Firefox Aurora with Developer tools
                Firefox Developer Edition
2 app: /home/jeffrey04/.local/share/applications/userapp-Firefox Developer Edition-8CCQV2.desktop - Custom definition for Firefox Developer Edition
                Firefox Developer Edition
Enter choice: :
Enter fullscreen mode Exit fullscreen mode

Enter a number, press enter, and the corresponding application launches (via gtk-launcher, yes, this script is not portable).

I wanted to somewhat replicate the UX of quicksilver, so I made it aware of the pipe character |, though it looks ugly in practice.

rc do echo lorem ipsum dolor sit amet "|" clipboard
Enter fullscreen mode Exit fullscreen mode

The specified text lorem ipsum dolor sit amet will then be copied to the clipboard. Unfortunately, I had to surround the pipe character with quotes so it will not be treated as a redirection in shell.

I am still figuring out the UX and specification, but for now it accomplished the main task where I want it to launch applications. After spending some time on it, and I reminded myself of Textual, where it offers an experience that resembles web front-end development. Currently, the TUI is still in development but seems to work similarly to the CLI counterpart.

It is hard to say what I expect out of it, as I am currently preparing to pick up some temporary part-time jobs while looking for the next project. This would greatly reduce the time and energy I have left for the project. The launcher does currently have a very basic support for plugins, but the API is subject to change.

Heroku

Amplify your impact where it matters most — building exceptional apps.

Leave the infrastructure headaches to us, while you focus on pushing boundaries, realizing your vision, and making a lasting impression on your users.

Get Started

Top comments (0)

Playwright CLI Flags Tutorial

5 Playwright CLI Flags That Will Transform Your Testing Workflow

  • --last-failed: Zero in on just the tests that failed in your previous run
  • --only-changed: Test only the spec files you've modified in git
  • --repeat-each: Run tests multiple times to catch flaky behavior before it reaches production
  • --forbid-only: Prevent accidental test.only commits from breaking your CI pipeline
  • --ui --headed --workers 1: Debug visually with browser windows and sequential test execution

Learn how these powerful command-line options can save you time, strengthen your test suite, and streamline your Playwright testing experience. Practical examples included!

Watch Video 📹️

👋 Kindness is contagious

Explore a trove of insights in this engaging article, celebrated within our welcoming DEV Community. Developers from every background are invited to join and enhance our shared wisdom.

A genuine "thank you" can truly uplift someone’s day. Feel free to express your gratitude in the comments below!

On DEV, our collective exchange of knowledge lightens the road ahead and strengthens our community bonds. Found something valuable here? A small thank you to the author can make a big difference.

Okay