sane-project-website/old-archive/1999-08/0213.html

140 wiersze
5.5 KiB
HTML
Czysty Zwykły widok Historia

<!-- received="Tue Aug 17 09:58:09 1999 PDT" -->
<!-- sent="Tue, 17 Aug 1999 18:38:31 +0200" -->
<!-- name="Oliver Rauch" -->
<!-- email="oliver.rauch@Wolfsburg.DE" -->
<!-- subject="Re: Starting a discussion about SANE and TWAIN..." -->
<!-- id="" -->
<!-- inreplyto="Starting a discussion about SANE and TWAIN..." -->
<title>sane-devel: Re: Starting a discussion about SANE and TWAIN...</title>
<h1>Re: Starting a discussion about SANE and TWAIN...</h1>
<b>Oliver Rauch</b> (<a href="mailto:oliver.rauch@Wolfsburg.DE"><i>oliver.rauch@Wolfsburg.DE</i></a>)<br>
<i>Tue, 17 Aug 1999 18:38:31 +0200</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#213">[ date ]</a><a href="index.html#213">[ thread ]</a><a href="subject.html#213">[ subject ]</a><a href="author.html#213">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0214.html">Oliver Rauch: "Re: SANE frames"</a>
<li> <b>Previous message:</b> <a href="0212.html">David Mosberger-Tang: "Re: SANE frames"</a>
<li> <b>Maybe in reply to:</b> <a href="0084.html">252353N@knotes.kodak.com: "Starting a discussion about SANE and TWAIN..."</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0237.html">252353N@knotes.kodak.com: "Re: Starting a discussion about SANE and TWAIN..."</a>
<!-- reply="end" -->
</ul>
<!-- body="start" -->
<a href="mailto:252353N@knotes.kodak.com">252353N@knotes.kodak.com</a> wrote:<br>
<p>
Hi Mark,<br>
<p>
<i>&gt; TWAIN doesn't really have any layers. At it's most</i><br>
<i>&gt; abstract description TWAIN is nothing more than an</i><br>
<i>&gt; elaborate conversion API between a standard name</i><br>
<i>&gt; space to a set of arbitrary native commands for some</i><br>
<i>&gt; given device.</i><br>
<p>
Yes, but which parts are bonded together?<br>
<p>
If I understand it right there is one source manager<br>
on a system. If we have two different scanners with<br>
two different drivers (sources), this source manager<br>
gets contact to the one or the other driver.<br>
<p>
I am able to select one source from one application<br>
and the second source from another application.<br>
<p>
Or is the source manager included into the application<br>
and each application has its own sourcemanager?<br>
<p>
How is the contact done, is the driver a library that is<br>
loaded on runtime?<br>
<p>
<p>
<i>&gt; This is why the notion of a sane.ds file is so appealing</i><br>
<i>&gt; to me.</i><br>
<p>
sane.DS? Did I miss a mail?<br>
<p>
<p>
<p>
<i>&gt; In this model TWAIN becomes an application</i><br>
<i>&gt; using SANE, and should therefore receive all the</i><br>
<i>&gt; benefits that any application using SANE would expect</i><br>
<i>&gt; to receive.</i><br>
<p>
Yes, and I don`t think it is a problem to add a<br>
TWAIN interface to an existing sane frontend.<br>
<p>
<p>
<i>&gt; However, if the sane.ds has the intelligence</i><br>
<i>&gt; to discover SANE devices on the network, then we gain</i><br>
<i>&gt; remote scanning control with no change to the TWAIN</i><br>
<i>&gt; spec (and more importantly, no changes to any TWAIN</i><br>
<i>&gt; applications).</i><br>
<p>
That is no problem, there is no difference for the frontend if<br>
it connects to a local backend or to the network backend<br>
that connects to a remote scanner.<br>
<p>
<p>
<i>&gt; I guess that's fundimental to my current notion of the best</i><br>
<i>&gt; implementation of a TWAIN using SANE and SANE</i><br>
<i>&gt; using TWAIN system. How much can we do to enable</i><br>
<i>&gt; applications access to more image capture devices</i><br>
<i>&gt; across more platforms, and do it with the applications</i><br>
<i>&gt; changing little or no code.</i><br>
<p>
Are you interested in programming code for unix,<br>
especally to implement the source manager and<br>
a test application? Of course we will work together<br>
but we need somone who is familiar with TWAIN.<br>
<p>
Andreas Beck and me also need help for creating<br>
the interface between the source selection manager<br>
and the sane frontend.<br>
<p>
Do you like to do this and do you have the time for it?<br>
<p>
<p>
Andreas and I talked how the communication by<br>
events between application and source can be<br>
implemented on unix.<br>
<p>
It looks like there are already differences between<br>
Windows and Mac.<br>
<p>
I have to read the TWAIN standard at first, but it will<br>
take a while (&gt;500 pages and less time).<br>
<p>
Do you already have the sane standard and source code<br>
example (you can download it from the sane homepage).<br>
If you have problems to read the formats of the files/archieves,<br>
let me now and I will convert them for you!<br>
<p>
<p>
Bye<br>
Oliver<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>
<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="0214.html">Oliver Rauch: "Re: SANE frames"</a>
<li> <b>Previous message:</b> <a href="0212.html">David Mosberger-Tang: "Re: SANE frames"</a>
<li> <b>Maybe in reply to:</b> <a href="0084.html">252353N@knotes.kodak.com: "Starting a discussion about SANE and TWAIN..."</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0237.html">252353N@knotes.kodak.com: "Re: Starting a discussion about SANE and TWAIN..."</a>
<!-- reply="end" -->
</ul>