I may indeed do that in the future. But hey, QtIrreco already has that feature; you don't have to wait for me to add it to Pierogi. And besides, the LIRC server (and QtIrreco is pretty much just a GUI on top of the LIRC server) was designed and built from the start to work off of config files provided by the user. Pierogi has been built in a completely different manner, incorporating keysets directly into the source code. Odds are, Pierogi will never have the kind of flexibility that an LIRC-based controller will have.

The flip side of this decision is that Pierogi can fairly easily do things like a power button search, something that the LIRC server will probably never be able to handle.

Well, actually, not really. (Warning -- long-winded discussion ahead! ) I started out grabbing LIRC config files (which have two internal formats -- those being raw IR timings, and slightly less raw IR timings ), but have since been grabbing files from the JP1 website (which generally uses files in either "KM" or "RM" formats that they've drawn up themselves, along with excel spreadsheets and simple textual lists of numbers), as well as a database of codes in the "Pronto" format (although I find those even more of a pain to decode). And, of course, there are individuals with either oscilloscopes or equivalent PC software all over the place who record the signals off of their own remotes and put them up on the net (like, say, Ken Shirriff's blog.)

I've kind of given up on supporting any of the various formats out there. The truth is, the original manufacturers start with a protocol, and then assign a number to each key on the remote. So, in Pierogi, I replicate this original protocol, and then rip the original manufacturer's numbers out of the various config file formats and store them as their original values. This has the benefit of being (a) much easier to store than how most of the formats out there do it (LIRC's raw timings can be painfully overblown), and (b), usually much easier to understand (as most manufacturers just start with the number 1 and work their way upwards key by key).

Anyway, check out the LIRC server -- it is fully supported on the N900 (it has been from the very start, I think), and provides a level of user control over IR codes that Pierogi will probably never be able to offer. Thanks!