Herb Peyerl wrote:
On Oct 10, 2008, at 5:55 AM, Jared D. McNeill wrote:Alan Barrett wrote:On Thu, 09 Oct 2008, Jared D. McNeill wrote:Here's the final remote API I'm proposing. Feedback?I don't know enough about this to give feedback on the API. However, I do have concern that the name "remote" seems confusing. Computers can have many types of remote connections or peripherals, and it's not at all clear from the name "remote" that a "remote control" is what's meant. I also don't care about the name, provided it's not confusing. I'd suggest some sort of abbreviation that incorporates parts of both words "remote" and "control".I thought about "rc", but that's even more confusing :) "irc" is still sort've confusing, and implies that the API is limited to IR devices.cube@ suggested zapper, which made me think of clicker also. Both seem kind've silly though..I'm sure we can brainstorm something that we can all agree on ;-)nirc?
Actually, if we limit the API to IR devices, we could hijack cir(4), which we have a man page for:
NAME
cir -- Consumer IR (remote control) driver
SYNOPSIS
cir* at XX?
HISTORY
The cir driver appeared in NetBSD 1.6.
BUGS
This device is not yet functional.
The userspace daemon can then be taught to speak both /dev/cir and
USB/bluetooth HID protocols.
Cheers, Jared