I realize this message is several months old, but let me answer it anyway:

I'll take a look around; I should be able to find something for it. Toshiba products are fairly well represented in the various universal remote sites.

Actually, I've decided not to retrieve any keyset data from the Psiloc irRemote website. I'm not entirely certain what their exact policy is on the use of config files downloaded from their site, but they certainly don't seem to be interested in free and open source software. (Even though, if you look at the format used by their config files, it's pretty obvious that it's been ripped straight out of the LIRC project. I'll bet they're even running the LIRC server inside their program...)

In any case, I suspect most of the available keyset data out there has already made its way into either the public LIRC project, or into the massive database of JP1 config files at the www.hifi-remote.com website. I doubt I'm missing much by excluding the Psiloc data.

(However, let me note that the QtIrreco project is itself built on top of the LIRC server, so Psiloc config files could be used with that project with only minimal reformatting, if you'd like to give it a try.)

This is, unfortunately, a bit of a problem. I really only started the Pierogi project for my own personal use, to let me play around with keyset data and try to merge commands for many different products into a smaller number of super-keysets. As such, I've not really bothered trying to create a user-friendly keyset management scheme; I've really just been hard-coding all the data directly into my source files. This does have the beneficial effect of allowing a lot of keyset data to be stored in a very small amount of space (which is, indeed, very good for a mobile machine; I'd love to see how much space the Psiloc program would take up if they tried to load every single one of their config files at the same time). But yeah, it doesn't make adding new keyset data easy for anybody who hasn't had their nose deep in the code for a while.

Honestly, I have to say I probably won't be changing this any time soon; I'm still having too much fun messing around with keyset data and trying to merge similar command sets together. Pierogi really is a different kind of beast than QtIrreco, irRemote, or any of the other LIRC-inspired (or -derived) IR programs; where they have focussed on flexibility, I'm concentrating more on size and efficiency. Anway, that's my excuse.