[lcdproc] definition of the project

[David Douthitt]

µ-thos wrote:
> 
> I tried to sum up the main ideas that were give in the last emails.

Very thoughtful!

> This is what I think LCDproc should look like:

I agree...

> Here are my thoughts of the client and server tasks:

> Server config file:
>        - map each input key from input drivers to a command, like:
>            key 'd' is sent to active client
>            keys 'a' to 'e' are sent to all clients
>            key 'm' activates 'Mail client'

This is an interesting idea.  I would suggest two things, howver:

1. Each key source is independent - so a key 'A' from driver 1 isn't the
same to the server as a key 'A' from driver 2.

2. Each key should have one and only one action - so only one client
should respond.

I could envision a set of "Actions" that are built-in, and have them
available to the drivers.

> Driver:
>        - each driver should be a seperate executable, that
>          gets input from / sends output to: /dev/<driver_name>
>        - only the driver should run as root
>        - each driver should have its own config file ???

I wouldn't want them to have their own config file.  Having separate
executables is interesting; however, it would change the entire
interface between the server and the driver, and requires some
substantial rewrites.  Also, rewriting the drivers should be taken with
caution - they come from many sources and are written by many different
people; if you change them completely all of the drivers and their
writers will have to come along.


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