sane-project-website/old-archive/1998-11/0224.html

64 wiersze
3.3 KiB
HTML

<!-- received="Mon Nov 23 09:31:31 1998 PST" -->
<!-- sent="Mon, 23 Nov 1998 09:31:26 -0800" -->
<!-- name="David Mosberger-Tang" -->
<!-- email="David.Mosberger@acm.org" -->
<!-- subject="Re: Too many options for xscanimage" -->
<!-- id="199811231731.JAA11667@panda.mostang.com" -->
<!-- inreplyto="36599902.ABEFC64F@wolfsburg.de" -->
<title>sane-devel: Re: Too many options for xscanimage</title>
<h1>Re: Too many options for xscanimage</h1>
<b>David Mosberger-Tang</b> (<a href="mailto:David.Mosberger@acm.org"><i>David.Mosberger@acm.org</i></a>)<br>
<i>Mon, 23 Nov 1998 09:31:26 -0800</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#224">[ date ]</a><a href="index.html#224">[ thread ]</a><a href="subject.html#224">[ subject ]</a><a href="author.html#224">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0225.html">Paul Walker: "RE: Too many options for xscanimage"</a>
<li> <b>Previous message:</b> <a href="0223.html">Oliver Rauch: "Re: Too many options for xscanimage"</a>
<li> <b>In reply to:</b> <a href="0112.html">: ""</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0231.html">Bernd Schroeder: "Re: Too many options for xscanimage"</a>
<li> <b>Reply:</b> <a href="0231.html">Bernd Schroeder: "Re: Too many options for xscanimage"</a>
<!-- reply="end" -->
</ul>
<!-- body="start" -->
<i>&gt;&gt;&gt;&gt;&gt; On Mon, 23 Nov 1998 18:18:58 +0100, Oliver Rauch &lt;<a href="mailto:oliver.rauch@Wolfsburg.DE">oliver.rauch@Wolfsburg.DE</a>&gt; said:</i><br>
<p>
Oliver&gt; I am working an a new frontend that solves this problem, but<br>
Oliver&gt; it will take some days until I can publish a<br>
Oliver&gt; pre-alpha-version of it. I think in 1-2 weeks I will have<br>
Oliver&gt; the first version ready. I will send a mail about it into<br>
Oliver&gt; the sane-devel-list!<br>
<p>
I'm not sure I'd call this "solved". Yeah, it solves the _space_<br>
issue, but not the complexity issue. There is a danger that SANE<br>
backend writers go "options nuts" and just make every knob and bit in<br>
a scanner a separate option without much thinking. In the interest of<br>
simplicity of use, we should pay attention to user interface design<br>
issues. Are the options we include really all needed? If not, how<br>
can we simplify things?<br>
<p>
(I'm not saying that the space issue shouldn't be solved. Maybe what<br>
we should do is just add a sentence or two to backend/GUIDE that<br>
talks about the user interface design issue.)<br>
<p>
--david<br>
<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="0225.html">Paul Walker: "RE: Too many options for xscanimage"</a>
<li> <b>Previous message:</b> <a href="0223.html">Oliver Rauch: "Re: Too many options for xscanimage"</a>
<li> <b>In reply to:</b> <a href="0112.html">: ""</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0231.html">Bernd Schroeder: "Re: Too many options for xscanimage"</a>
<li> <b>Reply:</b> <a href="0231.html">Bernd Schroeder: "Re: Too many options for xscanimage"</a>
<!-- reply="end" -->
</ul>