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

<!-- received="Tue Nov 24 08:27:47 1998 PST" -->
<!-- sent="Tue, 24 Nov 1998 17:26:56 +0100" -->
<!-- name="Oliver Rauch" -->
<!-- email="oliver.rauch@Wolfsburg.DE" -->
<!-- subject="Re: Too many options for xscanimage" -->
<!-- id="" -->
<!-- inreplyto="Too many options for xscanimage" -->
<title>sane-devel: Re: Too many options for xscanimage</title>
<h1>Re: Too many options for xscanimage</h1>
<b>Oliver Rauch</b> (<a href="mailto:oliver.rauch@Wolfsburg.DE"><i>oliver.rauch@Wolfsburg.DE</i></a>)<br>
<i>Tue, 24 Nov 1998 17:26:56 +0100</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#241">[ date ]</a><a href="index.html#241">[ thread ]</a><a href="subject.html#241">[ subject ]</a><a href="author.html#241">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0242.html">Oliver Rauch: "Re: Too many options for xscanimage"</a>
<li> <b>Previous message:</b> <a href="0240.html">Milon Firikis: "Re: Too many options for xscanimage"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
David Mosberger-Tang wrote:<br>
<p>
<i>&gt; &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>
<i>&gt;</i><br>
<i>&gt;   Oliver&gt; I am working an a new frontend that solves this problem, but</i><br>
<i>&gt;   Oliver&gt; it will take some days until I can publish a</i><br>
<i>&gt;   Oliver&gt; pre-alpha-version of it. I think in 1-2 weeks I will have</i><br>
<i>&gt;   Oliver&gt; the first version ready. I will send a mail about it into</i><br>
<i>&gt;   Oliver&gt; the sane-devel-list!</i><br>
<i>&gt;</i><br>
<i>&gt; I'm not sure I'd call this "solved".  Yeah, it solves the _space_</i><br>
<i>&gt; issue, but not the complexity issue.  There is a danger that SANE</i><br>
<i>&gt; backend writers go "options nuts" and just make every knob and bit in</i><br>
<i>&gt; a scanner a separate option without much thinking.  In the interest of</i><br>
<i>&gt; simplicity of use, we should pay attention to user interface design</i><br>
<i>&gt; issues.  Are the options we include really all needed?  If not, how</i><br>
<i>&gt; can we simplify things?</i><br>
<i>&gt;</i><br>
<i>&gt; (I'm not saying that the space issue shouldn't be solved.  Maybe what</i><br>
<i>&gt;  we should do is just add a sentence or two to backend/GUIDE that</i><br>
<i>&gt;  talks about the user interface design issue.)</i><br>
<i>&gt;</i><br>
<p>
Yes, you are absolutly right.<br>
I myself prefer only the absolute necessery options in the "Option"-window.<br>
E.g: the umax-backend supports a lot of options, but there is no scanner that really uses<br>
all of them and the less important ones are "advanced".<br>
I don't want to encourage the backend-programmes to push all options in one window,<br>
but I want to encourage them to implement as much functions of the scanner as possible.<br>
<p>
What I wanted do say is that there will be a frontend that can handle all options on small<br>
desktops, too.<br>
<p>
Bye<br>
Oliver<br>
<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="0242.html">Oliver Rauch: "Re: Too many options for xscanimage"</a>
<li> <b>Previous message:</b> <a href="0240.html">Milon Firikis: "Re: Too many options for xscanimage"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>