[Lcd4linux-devel] Re: [Fwd: Graphics support for Cwlinux]

[Xavier V. <xav...@fr...>]

> > As the command to put one pixel is at least 5bytes long and the
> > transfert rate is 19200, it takes about 30seconds to write all the
> > display :/
> I want to get to know the guy who designed this interface. I'd have some 
> wet towels with me...
lol

> > - It support also 'inverted text', that's a good thing, for example if a
> > temperature hits a predefined maximum value, you should add such and
> > option to the text widget (and use it if the display supports it)
> Good idea! Today another attribute came to my mind: blinking!
Yes ! Moreover, blink will be supported by all the displays ! But there
 should be a blink time somewhat low, not tick.

BTW, I tested "marquee text", it's great, but isn't there a way to make
it slide more quikly ? It's very slow.

> > Do you think it's possible to implement a time-based graph widget, and a
> > sort of 'fixed pixmap' widget (but which format to use for images ?) ?
> Everything is possible!
> - I want not only a time-based graph, but a general graph where x and y 
> can be any expressions.
I don't really understand what could be used as x value to get a
somewhat useable graph ?!

> - A "image" widget would be great! I'm going to prepare a photo of mine :-)
What a great usage ;) It could be used as icons (fixed or animated).
BTW, isn't there a way to toggle the display of an icon with some value
to emulate a GPO (add a visible attribute to any widget, and if the
expression is >0, display it).

> I'm not shure either. I think it does not make much of a difference what 
> kind of input you handle: a GPI, a tenmperature sensor, a fan sensor, or 
> a keypad. OTOH, the first would be all simple plugins or functions, the 
> latter should trigger an event.
> Hmmm... I think a GPI should be a function. And there sould be no 
> plugin_*.c for this, but the function should be inside of drv_Cwlinux.c 
> (as other plugins are at the moment, take a look at drv_MatrixOrbital).
Ok

> > There's still the problem of keypad handling, as the display sends the
> > keys directly, the driver should always be able to read this values.
> > Where can we implement this read ? directly drv ? plugin ? keypad.c ?
> Hmmm.. Give me some time on this issue. I've got three displays here 
> with a keypad, I'll have to go through all these datasheets, and try to 
> find a "common" solution.
At my side, I have the datasheet of the CW, but cwlinux didn't reply to
me :/ You got a CC of the mail I sent, didn't you ?

-- 
Xavier VELLO <xav...@fr...>