The one thing I can say about contributing keysets is that I've been trying to make Pierogi conform to the original manufacturer's protocols. This means that the actual numeric values intended for each command are used, and Pierogi does any necessary conversions or manipulations necessary to construct the associated infrared pulses.

In most protocols, you'll have a combination of a "device code" and a "command code". For example, there's an excellent collection of the Sony codes at http://www.hifi-remote.com/sony/, the only downside of which is that they don't keep track of which commands are associated with which devices. (This isn't as big a problem for Sony as for other manufacturers, as Sony does an amazing job of maintaining backwards-compatibility.) If you take a look at their television codes, you'll see they are arranged in tables, with each table labeled with a device code, and each row labeled with a command code. These device/command integers are exactly the ones used in Pierogi.

Ah, as someone fluent in C++, I've gotta admit that I'm quite comfortable with the classic Widget system. But yeah, it should be quite possible to place other front-ends onto Pierogi...