> > The other way round, i.e. a TWAIN frontend for SANE is trivial as
> > I understand. Why do not implement this as a first step?
>
> Yes. That's what I'm asking for. But it needs someone with good knowledge
> about the TWAIN API. I volunteer to help that person with all questions of
> SANE interfacing. To do it "right", we will need to define a "remote
> control API" for each architecture we want to run on, which will allow
> the TWAIN layer to interface with an arbitrary SANE frontend.
I am interested in adding a TWAIN-driver-level-interface to xsane.
> For having TWAIN style access to scanners on Unix (thus allowing application
> programmers to port their programs more easily), we'd need the
> abovementioned "remote control" for SANE frontends.
>
We should define a standard for the communication
between the TWAIN to SANE-FRONTEND wrapper
and sane frontends.
-- TWAIN-application layer
-> TWAIN-source-selection-layer
-> TWAIN to SANE-FRONTEND-wrapper
-> SANE-FRONTEND
-> ...
The wrapper and the standard has to be compatible to
all operating systems.
Bye
Oliver
-- EMAIL: Oliver.Rauch@Wolfsburg.DE WWW: http://www.wolfsburg.de/~rauch
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com