[lcdproc] input/output

[David Douthitt]

µ-thos wrote:
> 
> ok, first some more arguments for a standalone driver:

Note you said: "standalone" - this means it doesn't have to be an
executable.

> - easier to manage if more drivers come up
> - using alternative drivers

Same thing.

> - using alternative LCDd programms

True.

> - making an executable out of a driver is simple:
>   the main() function parses input an calls the apropriate procedure with
>   parameters

True.

> - as I mentioned, kernel drivers could be used

Hairy.... and what if one is using a kernel without kernel driver
support.  And how would you do this?  And what would you gain by making
your kernel more complicated yet?

> - linux is real multitasking (on a dual processor machine, the driver, client
>    and server could run on different cpus :) )

This hearkens to making LCDd multithreaded - and I wonder how useful
that would be.  I do know how complicated that would be (lots :)

> Next thing, what do you think about the idea to seperate input and output
> drivers?

I like that idea, but probably not the way you meant.  I think there
should be different interfaces within LCDd to support input drivers and
output drivers.  So a driver could be "input only" or "output only" or
both...


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