yatta VS clap-rs

I used Rust to prototype a new window manager in public and I found it very productive, easy to iterate on and make large changes without worrying about breaking anything.

Thanks! I had a look through the latest commit that you pushed to grist, and I noticed you handling errors from windows-rs in a similar way as I was doing in a previous project (yatta.

In general, I feel a lot better about this code base, the choice of data structures, and particularly the added safety around how I am calling unsafe Windows APIs in cleaner ways that allow me to propagate and handle errors when responding to WinEvents or socket commands (compare this mishmash to this much cleaner module!)

I wrote my very first window manager for Windows 10 in Rust earlier this here, I built it from the ground up using the new windows-rs crate. It was my first time developing anything for Windows and I was pleasantly surprised with the quality of the MS documentation ecosystem, and I also had a lot of great example code to learn from thanks to other projects like nog.

I am using this crate for a relatively non-trivial project (tiling window manager) and it has been pretty painless to use so far. From time to time, there will be an API or a type that is marked as not yet implemented, or an instance where the metadata it is generated from is incorrect, but the maintainer is helpful and responsive in my experience.

https://github.com/LGUG2Z/yatta/commit/87bc73eaa4f6ba7d00dbab2a6fb100f060b88ed8 Creating window floating rules based on partial title matching is added with this commit

I started working on yatta for Windows 10 because I was missing yabai and bspwm after I started working from a Windows 10 desktop last year.

I made a post about it on the Rust subreddit yesterday looking for more contributors: https://old.reddit.com/r/rust/comments/lh4uyq/yatta_bsp_tili...

It's still early days, but it has automatic tiling, gap control, focus switching, directional moving and tree orientation toggling and you can use AHK or any other hotkey daemon to manage your keybindings.

You still have to build it from source at the moment, but I'm hoping to have it installable via the Scoop package manager in a month or two.

https://github.com/LGUG2Z/yatta

I spent a couple of days hacking away to get something that works on Windows 10 with the bare minimum TWM functionality that my hands are used to, and I've managed to throw together Yatta: https://github.com/LGUG2Z/yatta (there is a demo gif on the readme).

We will be using the library for Clap - A simple-to-use, efficient, and full-featured library for parsing command line arguments and subcommands.

I recently came across this question (and associated answer) on the clap repository. The answer given is a good one. But I wanted to expand with my own findings and practices, which spurred the motivation for this post.

We can also use tuple-like struct syntax and named-field struct syntax for enum variants within our enum; this is because unlike in other OOP languages, Rust enums are actually sum types. You can read more about how powerful Rust enums are in another article we wrote here. You can have optional arguments by simply wrapping the types in Option, but if you want to add a flag to a command you can use bool, since clap recognises that flags are either there or not there. Let's have a look at what this might look like:

I began by developing a wrapper for the CurseForge API, which turned out to be a lengthy and challenging process but constituted the bulk of the work. Next, I coded the CLI, which was relatively straightforward. Instead of using the clap crate, a Rust tool for generating CLIs, I opted for the following line of code:

By this time I had already gotten tired of parsing arguments by myself and had looked for something to help with that. I found a really dang good argument parsing library called clap. What makes it so cool is it's largely declarative for common uses. You simply mark up a struct with attributes, and the parser automatically generates the usage and all the argument parsing code.

How CLI arguments are handled (using clap).

Is this just referring to wrapping based on the terminal width? That is supported with the wrap_help feature though I have been considering making it a default feature.

CLI, use Clap. If you want to get fancy, use Tui.

As our CLI is getting more complex, we'll use the clap crate to parse the command line arguments.