[lcdproc] TCP or .so

[Joris Robijn]

> 
> There was some discussion as to whether to send the entire framebuffer
> to the driver, or just send "paint" commands. Such that the differing
> amounts of customisable characters can be used more efficiently by
> devices that support them, etc. instead of making LCDd decide. This
> would mean each driver would have to have some form of widget
> implementation.

Yeah, or with graphical displays in the coming years. 

> Why not use hash tables? Using the parameter name as a key should
> guarantee fairly good spread as long as the hashing function is good
> enough. I worked out that passing each driver library, a hash of all the
> options under their [section] section in the config file, would allow

I hope you noticed that we were talking about the widget language. I 
could use a hash table here, it could speed things up.

> syntax. Any serial based devices have the port config as "8 N 9600" or

You're right, a port config string is a special string that should be 
scanned by the driver. Most values don't have such a special format. I 
would do most conversions centralised. Less chance of bugs. 

Joris

-- 
 Joris Robijn <joris@robijn.net>
 Home: 053 4311 553
 Mobile: 06 288 41 964

 // To understand recursion, we must first understand recursion


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