Thank you! I'm really not a UI guy, and so I've always been nervous that what works for me may be completely off for the public at large. (Which is why I always want to at least get the documentation straight before pushing anything up...)

Ah, well, that's the thing -- in Pierogi, the keysets are part of the actual executable. Looking at, say, an average LIRC config file, you might think that a keyset is a large, complicated beast; but the LIRC is protocol-agnostic, and does nothing but count raw IR pulses. Once you understand the protocol that a device is using, all you're left with is at most a few dozen integers -- one for each button on the given remote. I really saw no reason not to enter these directly into the code...

Ah, well, the problems with the QtIrreco app kind of steered me away from this path. Actually, I really am not a fan of most modern remote-control apps, even if all they are doing is downloading advertisements; I really think a simple tool like this should be fully independent, and work without needing to access the net for anything.

But yeah, I am looking at this concept for other projects...

For most projects, I would agree; however, given that IR keysets are tiny static sets of integers (as the devices being controlled generally do not support modifications to their controls), I still believe that in this case there's no downside to simply adding them directly to the code.

Hmm. Alright, well, they do say that "perfect is the enemy of good". Let me get the documentation into a relatively good shape, and push up what I've got...