[lcdproc] display connecting

[Matt]

Joris Robijn mentioned the following:

| If I don't have a keypad on my LCD, I can use a little program named 
| 'lcdkeys' for example to use any PC-keyboard as input. The program then 
| connects to LCDd, says it is a keypad, and transmits the keypresses as 
| I press the keys. When I press Q the program disconnects and ends.

Once the driver API is stable, you can write any number of Input drivers,
that take input from keyboard, joystick, wet finger across a parallel
port, whatever. As long as they generate events that conform to how
LCDproc wants them, then anything is realistically possible. Your driver
will claim it is an Input driver, and so LCDd will know that it will
export a known set of functions which can be used to grab keypress
events. What hardware you choose to generate events is up to you.

Alternatively, you can get LCDd to register a callback function with the
driver so it gets called when the driver detects an event, rather than
LCDd polling every so often. I don't know what might be possible.

| If I want to make a GIF of your display, a program (say lcdtogif) 
| connects to the net interface, and says it's a display with a flexible 
| size that should display the same contents as the existing display. The 
| new 'display-driver' will then get updated for the first time, and it 
| can produce a picture of the display as I wanted. Then it disconnects.

Again, you could write an Output driver that instead of writing to serial,
parallel, or i2c, it spits out GIFs, PNGs, whatever you want. You can use
the LCDd config file to control the rate of shots, directory to store
them, numbering convention, etc.

Matt



-----------------------------------------------------------
To unsubscribe from this list send a blank message to
lcdproc-unsubscribe@lists.omnipotent.net