HAL and scanners

[Étienne Bersac]

Hi,

> IMHO, a button handler is something for a desktop environment or a
> dedicated scan program; there are too many policy related questions
> than to place it into HAL or make the handler a Sane "core
> function".

HAL is able to tel apps that a device has been plugged. A similar event
must be sent by hal on scanner button press. This avoid desktop to
implement another dbus daemon for each session. Let the desktop decide
what to do with on this event. Also, such feature force software to open
the device; device access may be exclusive, SANE calls must be in one
software at one time.

> If you or Martin want to give these advanced (to avoid the word
> "bloat" ;) things a try nevertheless in the HAL context -- fine, but
> let's focus on the core topics that we can implement today with
> today's version of Sane and all its quirks:

The problem is to decide which software access SANE (which one do
sane_open() ). I'm against loading sane as app library like we do today.
Apps should only ask a daemon (either system wide or session wide) to do
the job. This allow the daemon to monitor the button state.

> today's version of Sane and all its quirks:

ACK ;)

> Specification of a minimal scanner namespace for HAL, collecting
> things that really must be added to Sane's scanner description
> files, like SCSI vendor/model strings etc.

ACK; keep up the good work :)

É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/b2c8a2f7/attachment.pgp