Re: Proposed widget type: image

On 21.02.2014 02:12, Stefan Herdler wrote:
> I don`t think it is a good idea to do ti that way, there are to many
> restrictions.
> The LCDd has to have access to the Image files of the client, which is
> not necessarily the case.
> On one machine, relative pathnames and file permissions might be an
> issue.
> Using this feature via LAN, would be quiet a hassle. One will need a
> local copy of all images on the server or a NFS or Samba share.
>
> I would prefer a simple 1bpp protocol to transfer the data from the
> client to the server instead.
> At the intended use with channel-logos, status "icons", etc. the
> amount of data will still be manageable, I think.
>
> A typical channel-logo of 4 x 2 characters will have about 500 pixels
> [2x4 x (8+1)x(5+1)]. This would be equivalent to about 65 characters
> and the logo wont change often. I'm pretty sure the LCDd will handle
> that easily, even if we have some additional overhead.
>
> Transfering only the pixels shown has several convenient side effects
> for us too.
> The code for reading an scaling the pictures is moved to the clients.
> So we don't have to deal with different picture-formats, scaling
> types,... and the Client has the full control what will be displayed.
>

Hi,

there are two things to keep in mind:

1. The original patch was for the glcd driver. For those graphical
driver you can use any size of an image and are not restricted to 8
characters.

2. LCDproc protocol is not designed for transmitting binary values. One
will need to encode/decode the image part somehow.

Still I believe, if we turn LCDproc into a program where the client
submits a fully client drawn image that is just displayed by the server,
one should use some other existing program that already has that feature.

Regards,
Markus