HAL and scanners

[Étienne Bersac]

Le samedi 30 décembre 2006 à 13:57 -0500, Joe Shaw a écrit :
> Hi,
> 
> Étienne Bersac wrote:
> > So the problem is how the app can give to SANE an udi ?
> 
> Well, that depends on the design.  If SANE is HAL-aware, then yeah, just 
> passing a UDI would be fine.  If not, then your API could be the wrapper 
> that provides SANE with the details that it got from HAL.  (This is how 
> libgphoto works, I believe.)

The problem is that sane device name highly depend on backend. frontend
can't do the mapping udi/sane name, that's crazy.

> I see.  It sounds like a good idea to generate the FDI files from the 
> SANE information, as was suggested by Abel earlier in the thread.  That 
> should give you the info you need, right?

Right.

Another solution should be to provide a tiny lib that do the hal<->sane
mapping, maybe shiped with sane. Then hal might even ignore the backend.
However, if hal can quickly determine the right backend, using a fdi,
this will save some cpu cycle (i hate that probe dialog).

Étienne.
-- 
Verso l'Alto !
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Ceci est une partie de message
	=?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
Url : http://lists.freedesktop.org/archives/hal/attachments/20061230/8298f42e/attachment.pgp