> I have comments.
Great!
> --
> In 3.2.2 Image Transmission you suggest that front ends provide some sort
> of means of warning or constraining the user from requesting frame formats
> that it does not support. I contend that this is not in general possible
> unless optional frame types can be enabled by a well-known option.
> Without a well-known option, the front end cannot know (in general)
> how to constrain the backend.
Yes, you may have noticed that the well-known options stuff hadn't changed
in my draft -- it needs a lot of work, especially given the comment below
There are two factors to concern ourselves about in controlling the data
format of a scanner, we could combine them or leave them as separate
options -- opinions about this are sought:
1. Type of data scanned (RGB, Grey, Lineart...)
2. Transmission format (interleaved RGB, JPEG, separate RGB, G32D)
There are already a lot of backends offering a control for the type of
scanning, but few (none?) control transmission format. The two are of
course interelated, but SANE can handle this quite nicely as it is.
> --
> In 4.5.4 Scan area options It might be nice to allow multiple scan
> areas for devices that support multiple scan areas per page. I know
> of a couple scanners that support such things.
>
> In addition, on scanners we build, each "window" of the page may have
> a different format (i.e. JFIF for the color and gray, TIFF/G4 for the
> bitonal) ant it would be nice to specify the frame type within the
> scan area specification.
Yes, not quite sure how we should do this... perhaps with
tl-x[1] ... tl-x[8] and format[1] ... format[8]
and the appropriate user-interface grouping (we can create Groups in
SANE options and expect the interface to do something sensible)
Then we also need a way to turn off windows we're not using.
This might take a bit longer to get right than I though ;)
Nick.
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com