kopia lustrzana https://gitlab.com/sane-project/website
180 wiersze
8.2 KiB
HTML
180 wiersze
8.2 KiB
HTML
|
<!-- received="Mon Aug 16 22:03:52 1999 PDT" -->
|
|||
|
|
<!-- sent="Wed, 11 Aug 1999 15:24:54 -0400" -->
|
|||
|
|
<!-- name="252353N@knotes.kodak.com" -->
|
|||
|
|
<!-- email="252353N@knotes.kodak.com" -->
|
|||
|
|
<!-- subject="Re: Discussion about SANE and TWAIN..." -->
|
|||
|
|
<!-- id="" -->
|
|||
|
|
<!-- inreplyto="Discussion about SANE and TWAIN..." -->
|
|||
|
|
<title>sane-devel: Re: Discussion about SANE and TWAIN...</title>
|
|||
|
|
<h1>Re: Discussion about SANE and TWAIN...</h1>
|
|||
|
|
<a href="mailto:252353N@knotes.kodak.com"><i>252353N@knotes.kodak.com</i></a><br>
|
|||
|
|
<i>Wed, 11 Aug 1999 15:24:54 -0400</i>
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#200">[ date ]</a><a href="index.html#200">[ thread ]</a><a href="subject.html#200">[ subject ]</a><a href="author.html#200">[ author ]</a>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0201.html">252353N@knotes.kodak.com: "Re: Discussion about SANE and TWAIN..."</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0199.html">Petter Reinholdtsen: "CVS unstable development tree"</a>
|
|||
|
|
<li> <b>Maybe in reply to:</b> <a href="0092.html">Oliver Rauch: "Discussion about SANE and TWAIN..."</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<li> <b>Next in thread:</b> <a href="0201.html">252353N@knotes.kodak.com: "Re: Discussion about SANE and TWAIN..."</a>
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|
|||
|
|
<!-- body="start" -->
|
|||
|
|
From: Mark McLaughlin<br>
|
|||
|
|
<p>
|
|||
|
|
Hi Oliver...<br>
|
|||
|
|
<p>
|
|||
|
|
Many thanks for your reply.<br>
|
|||
|
|
<p>
|
|||
|
|
I'm glad that you also see a benefit from this interaction between<br>
|
|||
|
|
SANE and TWAIN. The fact that TWAIN's user base is expressing<br>
|
|||
|
|
an interest in UNIX is a little daunting in some ways, since not many<br>
|
|||
|
|
of the current TWAIN members are doing anything with UNIX.<br>
|
|||
|
|
So one of the opportunities we see from working with SANE is a<br>
|
|||
|
|
chance to draw on your experience and expertise.<br>
|
|||
|
|
<p>
|
|||
|
|
As stated in my first message, I believe the principle benefit from<br>
|
|||
|
|
SANE and TWAIN working together is a chance to help app<br>
|
|||
|
|
writers cross from one OS to the other with less effort than it takes<br>
|
|||
|
|
today. So, TWAIN runs on UNIX, SANE runs on Windows, and<br>
|
|||
|
|
application writers have one less component to worry about<br>
|
|||
|
|
when trying to build their source code on an alternate platform.<br>
|
|||
|
|
<p>
|
|||
|
|
Bearing that in mind, I propose that on UNIX TWAIN runs in<br>
|
|||
|
|
communication with a generic Source that talks to SANE drivers.<br>
|
|||
|
|
We would have to make some minor changes to our Source<br>
|
|||
|
|
Manager to allow this to work properly, but such a TWAIN Source<br>
|
|||
|
|
would be able to communicate with any SANE supported image<br>
|
|||
|
|
capture device.<br>
|
|||
|
|
<p>
|
|||
|
|
At this time I don't believe there is much to be gained from having<br>
|
|||
|
|
a generic SANE driver that talks to TWAIN. Technically it is very<br>
|
|||
|
|
doable, but TWAIN Sources have a history of relying heavily or<br>
|
|||
|
|
even exclusively on their internal GUIs, which doesn't fit well into<br>
|
|||
|
|
SANE's programmatic design. We are working to change this<br>
|
|||
|
|
behavior (and have been since TWAIN 1.7 -- 1997), so in the<br>
|
|||
|
|
future it might be advantageous to do this.<br>
|
|||
|
|
<p>
|
|||
|
|
One question I have regarding SANE has to do with writing drivers<br>
|
|||
|
|
for mulitple UNIX platforms. Writing a 'single' device driver for<br>
|
|||
|
|
Solaris and AIX and Linux, etc must be appealing to some device<br>
|
|||
|
|
manufacterers (nobody wants to have write one driver per OS for<br>
|
|||
|
|
their device). Has SANE investigated an abstraction between<br>
|
|||
|
|
it's interface and the actual communication with the OS? I'm kind of<br>
|
|||
|
|
looking for something like ASPI (though wire independent). The<br>
|
|||
|
|
idea being that me, as a driver writer, would be able to write a<br>
|
|||
|
|
SANE driver that with a minimum of #ifdef's would be buildable on<br>
|
|||
|
|
UNIX or Macintosh or Windows platforms.<br>
|
|||
|
|
<p>
|
|||
|
|
If such a mechanism could be created, I would have a very good<br>
|
|||
|
|
reason for running SANE on Windows and Macintosh platforms...<br>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
Mark McLaughlin<br>
|
|||
|
|
Eastman Kodak Company<br>
|
|||
|
|
716 726 1352<br>
|
|||
|
|
<a href="mailto:mlm@kodak.com">mlm@kodak.com</a><br>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
Oliver Rauch <<a href="mailto:oliver.rauch@wolfsburg.de">oliver.rauch@wolfsburg.de</a>> on 08/11/99 01:01:30 PM<br>
|
|||
|
|
<p>
|
|||
|
|
To: <a href="mailto:sane-devel@mostang.com">sane-devel@mostang.com</a>, "McLaughlin, Mark" <mlm@kodak.com><br>
|
|||
|
|
cc: (bcc: Mark McLaughlin/252353/EKC)<br>
|
|||
|
|
Subject: Discussion about SANE and TWAIN...<br>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<a href="mailto:252353N@knotes.kodak.com">252353N@knotes.kodak.com</a> wrote:<br>
|
|||
|
|
<p>
|
|||
|
|
<i>> From: Mark McLaughlin</i><br>
|
|||
|
|
<i>></i><br>
|
|||
|
|
<i>> Hello...</i><br>
|
|||
|
|
<i>></i><br>
|
|||
|
|
<i>> My name is Mark McLaughlin, and I am the current Chairperson</i><br>
|
|||
|
|
<i>> on the TWAIN Working Group Technical Sub-committee. I am</i><br>
|
|||
|
|
<i>> sending this message to the manager for the SANE website in</i><br>
|
|||
|
|
<i>> the hope that it will reach the appropriate people.</i><br>
|
|||
|
|
<i>></i><br>
|
|||
|
|
<i>> There is growing interest (as viewed on our mailing list) for</i><br>
|
|||
|
|
<i>> seeing TWAIN support on UNIX platforms, particularly on Linux.</i><br>
|
|||
|
|
<i>> This interest has finally reached a level where the TWAIN</i><br>
|
|||
|
|
<i>> Working Group feels it needs to investigate the possibility of</i><br>
|
|||
|
|
<i>> adding support for UNIX.</i><br>
|
|||
|
|
<i>></i><br>
|
|||
|
|
<i>> We are interested in this because we believe there is an</i><br>
|
|||
|
|
<i>> opportunity to help developers of image capture systems</i><br>
|
|||
|
|
<i>> on UNIX, WIN32 and Macintosh platforms leverage their</i><br>
|
|||
|
|
<i>> code run on one or more or the alternate platforms.</i><br>
|
|||
|
|
<i>></i><br>
|
|||
|
|
<i>> TWAIN has no intention of competing with SANE. Rather we</i><br>
|
|||
|
|
<i>> wish to investigate a chance to employ the strengths of both</i><br>
|
|||
|
|
<i>> standards. We are not against the idea of seeing SANE</i><br>
|
|||
|
|
<i>> running on WIN32 or Macintosh platforms, and if there are</i><br>
|
|||
|
|
<i>> ways we can help SANE achieve this we would be happy to</i><br>
|
|||
|
|
<i>> discuss them. It is important that both groups benefit from any</i><br>
|
|||
|
|
<i>> interaction.</i><br>
|
|||
|
|
<i>></i><br>
|
|||
|
|
<i>> We would like to start a dialog with one or more members of the</i><br>
|
|||
|
|
<i>> SANE group to discuss this further. Please feel free to respond</i><br>
|
|||
|
|
<i>> directly to me, or to the TWAIN Working Group as a whole</i><br>
|
|||
|
|
<i>> (<a href="mailto:twain-wg@twain.org">twain-wg@twain.org</a>); whichever you feel to be more apropriate.</i><br>
|
|||
|
|
<p>
|
|||
|
|
Hello,<br>
|
|||
|
|
<p>
|
|||
|
|
we are interested in the discussion about making available TWAIN<br>
|
|||
|
|
on UNIX/linux and the coexistence of TWAIN and SANE on<br>
|
|||
|
|
the same operating systems.<br>
|
|||
|
|
I think there are a lot of thing both projects can benefit from.<br>
|
|||
|
|
It also is interesting to see if it makes sense/is possible<br>
|
|||
|
|
to make both standards work with each other<br>
|
|||
|
|
(e.g. create a sane-backend that connects to TWAIN devices<br>
|
|||
|
|
or to create a TWAIN device driver that makes available<br>
|
|||
|
|
the devices supported by SANE, etc.).<br>
|
|||
|
|
<p>
|
|||
|
|
At first I have to take a closer look at the TWAIN standard to<br>
|
|||
|
|
know what we are talking about.<br>
|
|||
|
|
<p>
|
|||
|
|
I will cc my mails to the sane-devel mailling list (so we can keep the<br>
|
|||
|
|
discussion open for the people who are involved or interested in the<br>
|
|||
|
|
sane development ). I will send the mails directly to you. If you like to<br>
|
|||
|
|
I will also cc my mails to <a href="mailto:twain-wg@twain.org">twain-wg@twain.org</a>.<br>
|
|||
|
|
<p>
|
|||
|
|
Bye<br>
|
|||
|
|
Oliver Rauch<br>
|
|||
|
|
<p>
|
|||
|
|
<pre>
|
|||
|
|
--
|
|||
|
|
EMAIL: <a href="mailto:Oliver.Rauch@Wolfsburg.DE">Oliver.Rauch@Wolfsburg.DE</a>
|
|||
|
|
WWW: <a href="http://www.wolfsburg.de/~rauch">http://www.wolfsburg.de/~rauch</a>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<p>
|
|||
|
|
<pre>
|
|||
|
|
--
|
|||
|
|
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
|
|||
|
|
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
|
|||
|
|
</pre>
|
|||
|
|
<!-- body="end" -->
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0201.html">252353N@knotes.kodak.com: "Re: Discussion about SANE and TWAIN..."</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0199.html">Petter Reinholdtsen: "CVS unstable development tree"</a>
|
|||
|
|
<li> <b>Maybe in reply to:</b> <a href="0092.html">Oliver Rauch: "Discussion about SANE and TWAIN..."</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<li> <b>Next in thread:</b> <a href="0201.html">252353N@knotes.kodak.com: "Re: Discussion about SANE and TWAIN..."</a>
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|