kopia lustrzana https://gitlab.com/sane-project/website
106 wiersze
5.4 KiB
HTML
106 wiersze
5.4 KiB
HTML
<!-- received="Fri Aug 13 23:03:19 1999 PDT" -->
|
||
<!-- sent="Sat, 14 Aug 1999 01:00:21 -0500 (CDT)" -->
|
||
<!-- name="Henry Miller" -->
|
||
<!-- email="hank@black-hole.com" -->
|
||
<!-- subject="Re: Starting a discussion about SANE and TWAIN..." -->
|
||
<!-- id="" -->
|
||
<!-- inreplyto="19990813165653.C663@rz.uni-duesseldorf.de" -->
|
||
<title>sane-devel: Re: Starting a discussion about SANE and TWAIN...</title>
|
||
<h1>Re: Starting a discussion about SANE and TWAIN...</h1>
|
||
<b>Henry Miller</b> (<a href="mailto:hank@black-hole.com"><i>hank@black-hole.com</i></a>)<br>
|
||
<i>Sat, 14 Aug 1999 01:00:21 -0500 (CDT)</i>
|
||
<p>
|
||
<ul>
|
||
<li> <b>Messages sorted by:</b> <a href="date.html#137">[ date ]</a><a href="index.html#137">[ thread ]</a><a href="subject.html#137">[ subject ]</a><a href="author.html#137">[ author ]</a>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0138.html">Andreas Beck: "Re: Starting a discussion about SANE and TWAIN..."</a>
|
||
<li> <b>Previous message:</b> <a href="0136.html">Kevin Charter: "Re: [net] connect_dev: major version mismatch: got 0, expected 1"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|
||
<!-- body="start" -->
|
||
On Fri, 13 Aug 1999, Andreas Beck wrote:<br>
|
||
<p>
|
||
<i>> > Don't forget that linux runs on more then intel x86 hardware. </i><br>
|
||
<i>> </i><br>
|
||
<i>> Sure. Once you have the source in SANE style, compiling for another platform</i><br>
|
||
<i>> is simple. The problem with getting source will be, that many manufacturers</i><br>
|
||
<i>> will be pretty reluctant to give it out.</i><br>
|
||
<i>> </i><br>
|
||
<i>> > and should not be ignored. Alpha (64 bits) and sparc (which is the other</i><br>
|
||
<i>> > endian if I remember right) present difficult problems if they are not</i><br>
|
||
<i>> > solved inheirantly in the design.</i><br>
|
||
<i>> </i><br>
|
||
<i>> Not really. Decently written software does not require much fuzzing around</i><br>
|
||
<i>> with endianness and data sizes.</i><br>
|
||
<p>
|
||
Not all software is decently written. It isn't particularry hard to write<br>
|
||
software that can run on any system regaurdless of byte order, but it<br>
|
||
isn't hard to mess up either. <br>
|
||
<p>
|
||
<i>> > Let me interrupt here and suggest Java. Not nessicatly the programing</i><br>
|
||
<i>> > languge as Sun has defined it (though that has advantages), but something</i><br>
|
||
<i>> > with a simielar goal: a simple API/Programing language that can be used</i><br>
|
||
<i>> > to create a backend. This will run on all platforms (ideally without the</i><br>
|
||
<i>> > endian issues that plague Sane today).</i><br>
|
||
<i>> </i><br>
|
||
<i>> I actually do not think, that interpreted bytecode is the greatest thing</i><br>
|
||
<i>> since sliced bread. O.K. - we are talking about scanners, that makes</i><br>
|
||
<i>> speed less of an issue usually, but I really do not think, we should waste</i><br>
|
||
<i>> lots of ressources interpreting bytecode, when all that is needed for</i><br>
|
||
<i>> getting a platform supported is ./configure;make;.</i><br>
|
||
<p>
|
||
I'm not the greatest fan of it either, but the idea has mert. And you<br>
|
||
already said above the problem with ./configure;make (manufactures won't<br>
|
||
release source, and don't expect the to help you out either if you try to<br>
|
||
attach your scanner to a Sun3 like I've considered)<br>
|
||
<p>
|
||
(as someone else suggested, this is called Jini, someone with connections<br>
|
||
should contact sun and see if we can get this part of the standard out<br>
|
||
soon. If Twain requires in the next release that all scanners do Jini it<br>
|
||
will go a long way towards the goal. [There are competing standards with<br>
|
||
Jini, so long as linux and xBsd support is easy to add I'm netural to<br>
|
||
which one is used])<br>
|
||
<p>
|
||
<i>> > serial ports in favor of Usb. (this probably isn't pratical yet, but a</i><br>
|
||
<i>> > footnote to suggest moving to USB) </i><br>
|
||
<i>> </i><br>
|
||
<i>> Note, that USB support in Unix is severly lacking.</i><br>
|
||
<p>
|
||
depends, the xBSDs have support in stable code, Linux is a bit behind, but<br>
|
||
that is promised. Only time will tell if USB lives up to the hype, but I<br>
|
||
keep hoping it does, but without the "We won't tell you how out scanner<br>
|
||
talks over the parrell port" that we face today.<br>
|
||
<p>
|
||
<i>> > I don't think Sane provides a network neighborhood type scanner brwoser,</i><br>
|
||
<i>> > but that would be a nice addition.</i><br>
|
||
<i>> </i><br>
|
||
<i>> No, it doesn't. It would be possible, though. The simplest way would be</i><br>
|
||
<i>> to autoprobe through the whole subnet. Other than that an announcement</i><br>
|
||
<i>> scheme would have to be invented.</i><br>
|
||
<p>
|
||
Hear that Twain team? this is one thing that Sane doesn't have that the<br>
|
||
unified standard should. <br>
|
||
<p>
|
||
<pre>
|
||
--
|
||
<a href="http://www.black-hole.com/users/henrymiller/">http://www.black-hole.com/users/henrymiller/</a>
|
||
<a href="mailto:hank@black-hole.com">hank@black-hole.com</a>
|
||
<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="0138.html">Andreas Beck: "Re: Starting a discussion about SANE and TWAIN..."</a>
|
||
<li> <b>Previous message:</b> <a href="0136.html">Kevin Charter: "Re: [net] connect_dev: major version mismatch: got 0, expected 1"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|