# Re: Too many options for xscanimage

David Mosberger-Tang (David.Mosberger@acm.org)
Mon, 23 Nov 1998 09:31:26 -0800

- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Paul Walker: "RE: Too many options for xscanimage"
- Previous message: Oliver Rauch: "Re: Too many options for xscanimage"
- In reply to: : ""
- Next in thread: Bernd Schroeder: "Re: Too many options for xscanimage"
- Reply: Bernd Schroeder: "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?

(I'm not saying that the space issue shouldn't be solved. Maybe what
we should do is just add a sentence or two to backend/GUIDE that
talks about the user interface design issue.)

--david

    --
    Source code, list archive, and docs: http://www.mostang.com/sane/
    To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

- Next message: Paul Walker: "RE: Too many options for xscanimage"
- Previous message: Oliver Rauch: "Re: Too many options for xscanimage"
- In reply to: : ""
- Next in thread: Bernd Schroeder: "Re: Too many options for xscanimage"
- Reply: Bernd Schroeder: "Re: Too many options for xscanimage"