From: Michael R. <re...@eu...> - 2004-08-02 10:34:51
|
Hi Ryan, > A while back I actually emailed one of the authors regarding > liblcd4linux. I was informed it was still in CVS and primarily created > to supply Python bindings. Right. it *used* to be there :-( > This support no longer seems to be present in CVS, nor is it in the > latest stable release. Where has it gone? I'm interesting in > developing an LCd based application using Python, and I'd hate to have > to write my own LCD access library, or even pull the necesary parts to > create one... The problem is, that due to the new layout (based on the evaluator), the corresponding layer in lcd4linux where liblcd4linux and the python bindings based upon is no longer present. As we were facing lots of problems with libtool, too, I decided to deactivate liblcd4linux temporarily. The new internal layout of lcd4linux uses very basic hardware display access functions; all of the special functions that various displays provide (GPIO's, contrast & backlight, fan reporting, ...) are implemented as 'plugins' to the evaluator. The display-specific stuff (drawing text, ...) itself is implemented as 'widgets'. Some displays need a regularly called timer function, too, which is implemented as a 'timer' in lcd4linux, which is triggered by the lcd4linux main loop. At the moment I have absolutely no idea where to find a common layer which liblcd4linux could provide to other applications. Yourt input and ideas are welcome! bye, Michael -- Michael Reinelt Tel: +43 676 3079941 Geisslergasse 4 Fax: +43 316 692343 A-8045 Graz, Austria e-mail: re...@eu... |