Re: Starting a discussion about SANE and TWAIN...

Andreas Beck (becka@rz.uni-duesseldorf.de)
Thu, 12 Aug 1999 21:03:02 +0200

> I suggest reaching these goals by making a pseudo-frontend which
> abstract the SANE API and present a TWAIN API and GUI to the
> application layer. Maybe my first diagram did not show the different
> levels of the TWAIN API and the SANE API. Here is another try:

I would actually prefer, if we coulf instead of

> +---------+------------+
> | SANE | TWAIN app |
> | +-------+----+
> | frontend| TWAIN | GUI|
> | | API +----+
> +---------+------------+
> | SANE backends |
> +----------------------+

do:

+-----------+
| TWAIN app |
+-----------+
| TWAIN API |
+-----------+
| glue layer|
+-----------+
| SANE |
| frontend |
+-----------+
| SANE |
| backends |
+-----------+

the glue layer I mention would basically be kind of a "remote control"
interface to the SANE frontends. That leaves us the ability to use
arbitrary frontends, instead of making one and putting that inside the
TWAI API layer.

> Currently, we hook up our scanners to the Unix server, but would like
> to access it from windows clients. Having a TWAIN source making this
> possible would solve our problems. :-)

WinSane is unfortunately not mature yet. But maybe it is a starting point.

I am sure the TWAIN people could help a lot in that area.

CU, Andy

-- 
= Andreas Beck                    |  Email :  <andreas.beck@ggi-project.org> =



--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com