David.Mosberger@acm.org said:
> Of course, a scanner vendor would want/need to provide a custom front
> end to be able to make use of these options. However, I think this is
> different from simply trying to write a fancy-looking custom frontend
> for the standard SANE options, so I think we should keep them
> separate.
Right.
(i) how to customize the look of the scanner dialog
Right and I think this is not a concern of SANE, but of the higher layer
that is TWAIN/Linux. All that sane needs (and already supports) is a
means to describe that option for automatic dialog generators, which
aren't expected to make it look as pretty as a custom one.
The SANE method is similar to (but more general then) the ISIS method.
(ii) how to provide an "escape" or "pass-through" mechanism that
permits for more extensibility (and how to do this without
completely breaking interoperability)
Right. SANE has already got that (to a degree) but only lacks an improved
means of sending different image formats. I believe a mechanism was proposed
in the last big discussion that supported this in a way that did not burden
generic applications.
In a nutshell, a new well known image format type was discussed, and the
SANE driver requireded to support a small subset [grayscale, RGB] in
addition to any other formats it adds. Simple and elegant. I think we
all agreed it was nifty, and will certainly accommodate the needs of
any scanner I can think of, without complexifying things like xscanimage.
-- Steve Williams "The woods are lovely, dark and deep. steve@icarus.com But I have promises to keep, steve@picturel.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Tue Aug 08 2000 - 07:59:26 PDT