Laurence Abbott a ?crit : > On Fri, 2005-05-13 at 17:44 +0200, Lucian Muresan wrote: > >>Nicolas Huillard wrote: >> >>>Lucian Muresan a ?crit : >>> >>>>even if it's off-topic on this list, the glcdlib driver I wrote for >>>>LCDproc emerged due to graphlcd which I heard of on this list first. You >>>>can have a look at http://www.muresan.de/graphlcd/lcdproc/ if you're >>>>interested. >>>>Many thanks go to Andreas Regel and the whole VDR developers and >>>>contributors. >>> >>>If I understand correctly the introduction on >>>http://www.muresan.de/graphlcd/lcdproc/, this driver allows lcdproc to >>>display things on a graphic LCD, but does not allow to use a text-based >>>LCD display with the graphlcd plugin (which seems obvious, stated like >>>this). >> >>Exactly. > > How does this differ from the graphlcd plugin? There is no relation with graphlcd, except for a certain part of a library. lcdproc is a framework allowing little scripts to display things on an LCD connected to the PC (typical use = internal temp, CPU load, quote of the day, etc.). This driver simply allows lcdproc to use the same LCD as the ones supported by graphlcd. No connection to VDR, hence the [OT]. LCD libraries and tools for Linux are beginning to become widespread and confusing... -- NH
