I played with GTK’s transitions a bit, but they don’t seem to support scaling-related transitions, so I don’t think you’ll be able to do that.

I was able to make a simple one: https://files.catbox.moe/okh3zc.mp4

Waybar uses GTK stylesheets for the theming. In theory, GTK CSS does have support for transitions and animations, which could be used in your case. But I’d say it’s a hard sell still. That aside I’ve never tried them in GTK, so I wouldn’t know if they even work in practice or how far.

I think you have a shot at this with eww instead. But it’s harder to work with and you’ll need to make somewhat complex scripts I’d imagine.

Alright. I pushed the changes to remote.

• https://github.com/eeriemyxi/dotfiles
• https://github.com/eeriemyxi/dotfiles/blob/main/.config/waybar

NOTE: Waybar has a built-in module for showing temperature, it’s just that I couldn’t make it work for me and that’s why I have a custom module to show CPU temperature. I recommend that you try the built-in one first (since it might work on your machine) for more minimal setup.

I’m almost there, I think. I’ll let you know in an hour or two.

Eventually I’m going to push it my dotfiles Git repository, but right now I’m still figuring out the theming so it’s not up yet.

I’m using Waybar for the system bar. It should work on most Wayland compositors.

Yeah I usually love Python but right now I’m working on a paid project where I need to deal with tasks that are critical to mostly work on first try. Now, if it would be a different matter if my code was just completely idiotic and still worked but Python doesn’t error even when there is obvious typo that any statically compiled language could’ve picked up on a breeze at compile time.

I am scared to even implement a better logging system in my program because sometimes I forget to sanitize the arguments and my program fucking crashes at runtime because I added a new fucking logging statement.

I so fucking wish I had static type checking right now. The libraries I am using doesn’t have types (via annotations) so unless I spend days fixing their shit, I will have to continue with these shitty runtime crashes for the shittiest small mistakes. I also can’t trust these annotations because even if they are “wrong” their code coul perfectly work fine and they could even ship the wrong types. I would have the burden of dealing with their shitty annotations if that happens.

If anybody is curious, it’s a real preprocessor for Python called PyGyat.

Vert guarantees a single file/directory when you extract something with it. If there are more than 1 file in the archive it will nest them in a directory. I have no plans to add any flags or anything to make it extract without nesting either.

So it detects if there’s a single folder inside the zip containing all the files or all the files directly inside the zip?

Yes. It also has l (lowercase L) subcommand which lists the contents of the archives to the terminal (stdout).

UPDATE: Implemented VERT_USE_EXTERNAL_TOOLS environment variable. See #Configuration.

I had passed the filter parameter as "data", which should help prevent most issues with it but yes I agree that it would’ve been better to use external tools to do the heavy-lifting. I avoided them to make the program cross-platform and easier to setup (you currently can just run a simple pip command to install it). I may introduce them as optional backends later with a warning on the default ones but for now I’m postponing it.