quicktile VS x11rb

You might wanna have a look at quicktile. It's basically an addon that adds tiling to existing WM. Works well, but lacks some of the intrgrations dedicated tiling WM have.

As the author of QuickTile, which is written in Python but even closer to what you describe than a window manager would be, I have to say that, yeah, doing X11 stuff takes a lot of knowledge that's not ideally documented in non-print sources.

quicktile is a handy tiling tool which saves me a lot of time. native custom tiling is always better tho

It's been a long time since I bothered with this functionality, but I seem to recall that quicktile was a better fit for me than those other two. Not sure if it's still viable.

Actually, I plan to add a .nojekyll file and then use something like Pelican with custom plugins, then set GitHub Actions to run my update.sh on push... similar to how http://ssokolow.com/quicktile/ is a Sphinx-based site hosted on GitHub Pages and automatically regenerated from the pushed sources.

I've been using ssokolow.com/quicktile for this purpose, it does what I need and doesn't replace the wm.

If you're into using shortcuts I would recommend installing Quicktile for manage your windows: https://github.com/ssokolow/quicktile

you can try quicktile

The best I could do for the API documentation for this project of mine was to use the automodule directive to autogenerate at the coarsest level possible and remember to never create new .py files if I could possibly avoid it.

xdotool worked ... but I didn't want to depend on external command-line tools, so I decided to look for X11 bindings for Rust. The best library I could find was x11rb. It had very little documentation and almost no one used it (it was difficult to find people who could help me with it). Fortunately, it had a detailed tutorial. Still, it was a struggle to make things works sometimes.

I'm using x11rb, X11 Rust Bindings. I modified some code from this tutorial so that I'm listening to key presses from parent_win (screen.root) rather than win:

In the end, I decided to use x11rb: https://github.com/psychon/x11rb. This way I don't have to run external commands.

I'm trying to move a window (the GNOME terminal) with x11rb. I followed this tutorial. But the move_window function doesn't move the window.

I'm using x11rb to interact with a window created with gtk-rs. window_id is the ID of the window created with gtk-rs. window_id_2 is the ID of the window created with x11rb (for testing purposes).

I also checked x11rb, but I think it's too low level (and too complicated).

There is a comparison page in x11rb but it seems to be outdated w.r.t rust-xcb and the unsafe claims, so would appreciate other perspectives.

Do you have a source for that or any specifics on how it "can't handle" the usecases? There's already work in Rust around fully supporting X11 (for example https://github.com/bread-graphics/breadx or https://github.com/psychon/x11rb)

I was thinking about specializing x11rb which is a great library for interfacing with X11, to my specific single threaded use case.

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.