penrose VS pgwm

writing an X11 window manager is ... extremely tedious. have a look at https://github.com/sminez/penrose .

Hey everyone 👋 ! I'm currently working on a rust library for building and configuring your own shell! It's inspired by projects like xmonad and penrose where the configuration of the program is done in code. This means that for example, instead of using Bash's arcane syntax for configuring the prompt, it can be configured instead using a rust builder pattern! The project itself is still at a very young stage, so there are plenty of bugs and unimplemented features. However, some things that are (partially) implemented are:

https://github.com/sminez/penrose https://sminez.github.io/penrose/

im not sure weather or not i should mention penrose an dwm here :D you can configure even more than with kde (and my setup ended up way beyond anything recognisable)

There are many existing tiling-window managers with i3 probably being the most popular choice for linux systems. These window managers can depend on extensive configuration files or in the case of dwm, git patching or C programming. Penrose takes a different approach in that Penrose is not a window manager. Penrose is a high-level rust library that you use to build your own window manager. This gives us many options for customization while also giving us all the advantages that come with writing rust code.

Mostly non-dynamic except for wm-specific actions. What kind of events are we talking about? I think that if we're talking about something that on a more low-level exposes x11 events penrose is a better bet. That being said, exposing something like:

You might find Penrose interesting. Basically a rust library that you can use to write your own X11 window manager without needing to deal with a lot of the lower level details of X11.

https://github.com/sminez/penrose which I'm really enjoying so far.

Ps. I don't at all endorse using tiny-std, I think it's correct but I wouldn't be surprised if some nasty bugs are hiding somewhere in there. Although I do use it for my WM pgwm which can now be build on stable, assuming you're running Linux with io-uring, a wrote a bit about that change here but didn't post about it then. The main benefit of tiny-std being tiny binaries that link statically.

If you want to check out the WM, that can be found here. If you want to check out tiny-std, that's here. As previously mentioned, there's a write-up on all of that here.

So if firefox is an application you can find you can query the WM_CLASS property, like this. Other applications might not set that and you'd have to use some other property or information to deduce that this given window(which is just a u32) is actually applicationA. A tip is to start the application, use xprop and see what properties it sets. call_wrapper.rs contains a lot of code about querying different properties. The x11rb example simple_window.rs has a few examples of the other side of that showing how an application can set its on properties.