Paul Walker
> -----Original Message-----
> From: David Mosberger-Tang [SMTP:David.Mosberger@acm.org]
> Sent: Monday, November 23, 1998 9:31 AM
> To: sane-devel@mostang.com
> Subject: Re: Too many options for xscanimage
>
> >>>>> On Mon, 23 Nov 1998 18:18:58 +0100, Oliver Rauch
> <oliver.rauch@Wolfsburg.DE> said:
>
> Oliver> I am working an a new frontend that solves this problem, but
> Oliver> it will take some days until I can publish a
> Oliver> pre-alpha-version of it. I think in 1-2 weeks I will have
> Oliver> the first version ready. I will send a mail about it into
> Oliver> the sane-devel-list!
>
> I'm not sure I'd call this "solved". Yeah, it solves the _space_
> issue, but not the complexity issue. There is a danger that SANE
> backend writers go "options nuts" and just make every knob and bit in
> a scanner a separate option without much thinking. In the interest of
> simplicity of use, we should pay attention to user interface design
> issues. Are the options we include really all needed? If not, how
> can we simplify things?
>
[Paul Walker] I appreciate simplicity in a user-interface, but
I also like knowing all of the options that are available. Perhaps an
extended help option could be added, so that the "advanced" options
would not be listed unless they are specifically requested.
[...]
> --david
>
> --
> Source code, list archive, and docs: http://www.mostang.com/sane/
> To unsubscribe: echo unsubscribe sane-devel | mail
> majordomo@mostang.com
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com