kopia lustrzana https://gitlab.com/sane-project/website
67 wiersze
2.8 KiB
HTML
67 wiersze
2.8 KiB
HTML
<!-- received="Sun Aug 15 17:55:43 1999 PDT" -->
|
||
<!-- sent="Mon, 16 Aug 1999 01:55:43 +0100 (GMT)" -->
|
||
<!-- name="Nick Lamb" -->
|
||
<!-- email="njl98r@ecs.soton.ac.uk" -->
|
||
<!-- subject="Re: SANE V2" -->
|
||
<!-- id="" -->
|
||
<!-- inreplyto="37B74E99.2FF4C31F@martoneconsulting.com" -->
|
||
<title>sane-devel: Re: SANE V2</title>
|
||
<h1>Re: SANE V2</h1>
|
||
<b>Nick Lamb</b> (<a href="mailto:njl98r@ecs.soton.ac.uk"><i>njl98r@ecs.soton.ac.uk</i></a>)<br>
|
||
<i>Mon, 16 Aug 1999 01:55:43 +0100 (GMT)</i>
|
||
<p>
|
||
<ul>
|
||
<li> <b>Messages sorted by:</b> <a href="date.html#186">[ date ]</a><a href="index.html#186">[ thread ]</a><a href="subject.html#186">[ subject ]</a><a href="author.html#186">[ author ]</a>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0187.html">Tom Martone: "Re: SANE V2"</a>
|
||
<li> <b>Previous message:</b> <a href="0185.html">Tom Martone: "Re: SANE frames"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|
||
<!-- body="start" -->
|
||
On Sun, 15 Aug 1999, Tom Martone wrote:<br>
|
||
<p>
|
||
<i>> Here's an example of the stuff the bh backend writes:</i><br>
|
||
<p>
|
||
[XML snipped]<br>
|
||
<p>
|
||
Now I'm really starting to see why you want FRAME_ASCII or whatever...<br>
|
||
If this is the volume of data being sent, I guess frames are the way<br>
|
||
to go.<br>
|
||
<p>
|
||
<i>> Another use of the text frame might be to allow the backend to </i><br>
|
||
<i>> report its configuration. Wouldn't it be nice if the backend information</i><br>
|
||
<i>> shown in the Xsane dialog could include a little text area that simply</i><br>
|
||
<i>> displayed a textual summary of the scanner's inquired</i><br>
|
||
<i>> configuration and capabilities? This would be especially useful if</i><br>
|
||
<i>> the scanner were being accessed through saned. I don't know the mechanism </i><br>
|
||
<i>> by which the front end would ask for this, though. </i><br>
|
||
<p>
|
||
Hmm. I think what you're talking about here is stuff already better<br>
|
||
handled in SANE Options. Have you looked at that stuff in SANE 1.0?<br>
|
||
I think it's a very powerful way to express anything a user might want<br>
|
||
to know, and more, about the scanner's current state of mind.<br>
|
||
<p>
|
||
Also, in SANE Options it's clear which stuff you can change, and which<br>
|
||
stuff you can't -- there's even a way to say "The user can change this,<br>
|
||
but only by {pressing a button, flipping a dipswitch, opening a panel}<br>
|
||
on the scanner itself.<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="0187.html">Tom Martone: "Re: SANE V2"</a>
|
||
<li> <b>Previous message:</b> <a href="0185.html">Tom Martone: "Re: SANE frames"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|