On Fri, 17 Mar 2000, Oliver Rauch wrote:
OR >The problem is that the Windows TWAIN API depends on the Windows API (IPC).
OR >The TWAIN org wanted to implement the same API for unix what would be
very bad.
OR >The problem is that on windows the driver is a part of the
frontend-process and so all
OR >events have to be passed through to the backend.
OR >
OR >There already is a second TWAIN interface for the apple mac that is not
compatible to
OR >the windows TWAIN API.
OR >
OR >We suggested to create a unix TWAIN API that is as compatible as possible
to the WIN TWAIN
OR >but with some differences that use the special functions of unix systems.
OR >
OR >I still would like to add a WIN and a UNIX TWAIN API to xsane but in the near future I do not
OR >have the time to work on it.
OR >
OR >After all: it is not so simple like it looks at first.
This is true. If you think that there is another TWAIN interface, built
for OS/2 by two software manufacturers (commercial software), the idea is
even more complicated.
Ciao,
-- Mentore Siesto Team OS/2 Italia Home page: http://www.geocities.com/Tokyo/Temple/8529/index.html-- 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 : Fri Mar 17 2000 - 01:46:37 PST