kopia lustrzana https://gitlab.com/sane-project/website
78 wiersze
3.5 KiB
HTML
78 wiersze
3.5 KiB
HTML
<!-- received="Mon May 10 06:36:05 1999 PDT" -->
|
||
<!-- sent="Mon, 10 May 1999 14:34:52 +0100 (GMT)" -->
|
||
<!-- name="Nick Lamb" -->
|
||
<!-- email="njl98r@ecs.soton.ac.uk" -->
|
||
<!-- subject="Re: [Announce] WinSANE 0.1.0.0 Release" -->
|
||
<!-- id="" -->
|
||
<!-- inreplyto="009101be9a97$36c0d960$499672cf@sunshinecomputing.com" -->
|
||
<title>sane-devel: Re: [Announce] WinSANE 0.1.0.0 Release</title>
|
||
<h1>Re: [Announce] WinSANE 0.1.0.0 Release</h1>
|
||
<b>Nick Lamb</b> (<a href="mailto:njl98r@ecs.soton.ac.uk"><i>njl98r@ecs.soton.ac.uk</i></a>)<br>
|
||
<i>Mon, 10 May 1999 14:34:52 +0100 (GMT)</i>
|
||
<p>
|
||
<ul>
|
||
<li> <b>Messages sorted by:</b> <a href="date.html#71">[ date ]</a><a href="index.html#71">[ thread ]</a><a href="subject.html#71">[ subject ]</a><a href="author.html#71">[ author ]</a>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0072.html">Brian Macy: "Re: [Announce] WinSANE 0.1.0.0 Release"</a>
|
||
<li> <b>Previous message:</b> <a href="0070.html">Brian Macy: "[Announce] WinSANE 0.1.0.0 Release"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|
||
<!-- body="start" -->
|
||
On Sun, 9 May 1999, Brian Macy wrote:<br>
|
||
<p>
|
||
<i>> Things I really could use help/info on:</i><br>
|
||
<i>> - Why endian matters when do the actual scan. From everything I can tell the</i><br>
|
||
<i>> scan data is all byte oriented so endianess doesn't matter.</i><br>
|
||
<p>
|
||
For a bit-oriented scan (lineart) you can safely assume everyone is agreed<br>
|
||
about which order the bits go in. Networks transfer a byte at a time.<br>
|
||
<p>
|
||
For a byte-oriented scan (8-bit grey, 24-bit colour) there's also nothing<br>
|
||
to worry about, we're all agreed how to send a byte over a network.<br>
|
||
<p>
|
||
However, multi-byte samples (10 bit grey, 36 bit colour etc.) require<br>
|
||
that you compare your endianess with the backend, and if they're different<br>
|
||
convert. This ONLY applies to image data, everything else uses network<br>
|
||
byte order to solve this problem.<br>
|
||
<p>
|
||
If (as I suspect) this version of WinSANE doesn't support anything bigger<br>
|
||
than 8-bit samples, (ie 24-bit colour) then you needn't worry about it.<br>
|
||
<p>
|
||
<i>> - TWAIN DLL... I know almost nothing about TWAIN and nothing about</i><br>
|
||
<i>> implementing a TWAIN DLL. I don't have the time to really figure it out</i><br>
|
||
<i>> either so without help it will never progress to be a TWAIN DLL.</i><br>
|
||
<p>
|
||
Hmm. The TWAIN toolkit, at least in recent versions looked like a pretty<br>
|
||
straight forward "fill in the blanks" piece of software. I can't offer to<br>
|
||
help here (no Win32 experience, and no desire to get some) but I suspect<br>
|
||
that plugging your GUI onto TWAIN is pretty easy.<br>
|
||
<p>
|
||
Since SANE already handles all the fiddly decisions about how to express<br>
|
||
scanner capabilities, in the backend, you'll probably have less work to<br>
|
||
do than someone implementing TWAIN for a single device... I hope.<br>
|
||
<p>
|
||
<i>> Adds support for LineArt, HalfTone, and GrayScale</i><br>
|
||
<i>> Allows selecting of device on remote host</i><br>
|
||
<i>> Allows selecting of Scan Mode</i><br>
|
||
<p>
|
||
Hooray!<br>
|
||
<p>
|
||
Nick.<br>
|
||
<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="0072.html">Brian Macy: "Re: [Announce] WinSANE 0.1.0.0 Release"</a>
|
||
<li> <b>Previous message:</b> <a href="0070.html">Brian Macy: "[Announce] WinSANE 0.1.0.0 Release"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|