[lcdproc] Multiple inputs and outputs and clients OH MY!
Wed, 19 Sep 2001 18:22:37 +0200
David Douthitt wrote:
> email@example.com wrote:
>> --- firstname.lastname@example.org wrote ---
>>> OK, question: Do you really (now be honoust) really want to couple
>>> these displays to become one large display ? Or do you use the
>>> displays all for different functions/programs, so they could better use
>>> a separated server ?
>> This one woke me up a bit. I hadn't even thought of this to keep things
>> simple and easy to cope with.
>> One display per server. Make server configurable enough that it can be run
>> more than once without stepping on other instances of it.
> Also, there IS a distinction between using only ONE display driver per
> LCDd invocation and between using multiple displays in the DRIVER.
How about a kind of "driver-wrapper"? Maybe one could write one
fake driver - the "wrapper" - that does everything LCDd wants it to.
So when writing the real server code you would no longer have to think
about the driver(s) that is (are) really used.
For a user attaching several displays to LCDd would be like telling the
driver-wrapper which drivers to use with maybe different settings.
I know this could be done by changing the server code, too, but this
way it'd be more like splitting things up. And again it'd be like
a client/server concept, but this time LCDd is the client.
Another idea might be to make writing a driver easier than it is
already. Maybe one could create a kind of toolbox you could
use to put support for several displays into one single driver.
This way a user could decide, how to make one unit of several
displays or something like that.
Hope it helps,
To unsubscribe from this list send a blank message to