sane-project-website/old-archive/2000-08/0075.html

143 wiersze
6.0 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
"http://www.w3.org/TR/REC-html40/loose.dtd">
<HTML>
<HEAD>
<TITLE>sane-devel: Re: quick note from the TWAIN/SANE meeting at OLS</TITLE>
<META NAME="Author" CONTENT="Oliver Rauch (oliver.rauch@Wolfsburg.DE)">
<META NAME="Subject" CONTENT="Re: quick note from the TWAIN/SANE meeting at OLS">
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<H1>Re: quick note from the TWAIN/SANE meeting at OLS</H1>
<!-- received="Tue Aug 8 10:35:17 2000" -->
<!-- isoreceived="20000808173517" -->
<!-- sent="Tue, 08 Aug 2000 19:36:43 +0200" -->
<!-- isosent="20000808173643" -->
<!-- name="Oliver Rauch" -->
<!-- email="oliver.rauch@Wolfsburg.DE" -->
<!-- subject="Re: quick note from the TWAIN/SANE meeting at OLS" -->
<!-- id="3990452B.D8E9DA40@wolfsburg.de" -->
<!-- inreplyto="200008041708.KAA18751@panda.mostang.com" -->
<STRONG>From:</STRONG> Oliver Rauch (<A HREF="mailto:oliver.rauch@Wolfsburg.DE?Subject=Re:%20quick%20note%20from%20the%20TWAIN/SANE%20meeting%20at%20OLS&In-Reply-To=&lt;3990452B.D8E9DA40@wolfsburg.de&gt;"><EM>oliver.rauch@Wolfsburg.DE</EM></A>)<BR>
<STRONG>Date:</STRONG> Tue Aug 08 2000 - 10:36:43 PDT
<P>
<!-- next="start" -->
<LI><STRONG>Next message:</STRONG> <A HREF="0076.html">Oliver Rauch: "xsane-win32-0.61 works on Windows NT"</A>
<UL>
<LI><STRONG>Previous message:</STRONG> <A HREF="0074.html">Henning Meier-Geinitz: "Re: Are we ready for a new release?"</A>
<LI><STRONG>In reply to:</STRONG> <A HREF="0047.html">David Mosberger-Tang: "Re: quick note from the TWAIN/SANE meeting at OLS"</A>
<!-- nextthread="start" -->
<!-- reply="end" -->
<LI><STRONG>Messages sorted by:</STRONG>
<A HREF="date.html#75">[ date ]</A>
<A HREF="index.html#75">[ thread ]</A>
<A HREF="subject.html#75">[ subject ]</A>
<A HREF="author.html#75">[ author ]</A>
</UL>
<HR NOSHADE><P>
<!-- body="start" -->
<P>
David Mosberger-Tang wrote:
<BR>
<P><EM>&gt; It is interesting how scanner vendors insist on writing their own
</EM><BR>
<EM>&gt; frontends. Graphics cards vendors seem to be able to live with the
</EM><BR>
<EM>&gt; fact that, on Windows, all they can do is add a couple of tabs to the
</EM><BR>
<EM>&gt; &quot;Display Properties&quot; dialog. I think the Graphics card approach is
</EM><BR>
<EM>&gt; MUCH better because it gives users a (mostly) consistent user
</EM><BR>
<EM>&gt; interface, while still giving vendors a certain level of
</EM><BR>
<EM>&gt; differentiation.
</EM><BR>
<EM>&gt;
</EM><BR>
<EM>&gt; I think if TWAIN were to become widespread on non-Windows/non-Mac
</EM><BR>
<EM>&gt; platforms, vendors would sooner or later realize that it's just not
</EM><BR>
<EM>&gt; practical to write a custom frontend for each case. What we can offer
</EM><BR>
<EM>&gt; to them is to give up some (not all!) of the control over the look of
</EM><BR>
<EM>&gt; the scanner dialog in return for not having to worry about the scanner
</EM><BR>
<EM>&gt; dialog ever again. Given how scanner prices have dropped over the
</EM><BR>
<EM>&gt; last couple of years, I'm quite sure there must be _some_ vendors that
</EM><BR>
<EM>&gt; would go for this deal.
</EM><BR>
<P>I think it is good enough that the vendors can write their own frontends
<BR>
- if they really like an own interface. We should not support too much
<BR>
that the frontends do look different for each backend. For the user it
<BR>
is much better if we have a common interface.
<BR>
<P><EM>&gt;
</EM><BR>
<EM>&gt; Different &quot;skins&quot; (themes) are also a way to make a dialog look more
</EM><BR>
<EM>&gt; unique without even changing how the interface works. Anyhow, making
</EM><BR>
<EM>&gt; the user-interface scriptable certainly would require some thought.
</EM><BR>
<EM>&gt; It's of course a chicken-and-egg problem. It would help greatly if we
</EM><BR>
<EM>&gt; had one or two scanner vendors that would be willing to work with us,
</EM><BR>
<EM>&gt; so we can make sure that the work wouldn't be wasted.
</EM><BR>
<P>We could add some &quot;reserved&quot;, &quot;vendor specific&quot; or &quot;style-info&quot; fields to
<BR>
the options to sane-standard 2.0. There is no need to specify it from the
<BR>
beginning, it can be marked as &quot;reserved for future use&quot; and defined
<BR>
when there is a need for it.
<BR>
<P>Bye
<BR>
Oliver
<BR>
<P><P><PRE>
--
Homepage: <A HREF="http://www.wolfsburg.de/~rauch">http://www.wolfsburg.de/~rauch</A>
sane-umax: <A HREF="http://www.wolfsburg.de/~rauch/sane/sane-umax.html">http://www.wolfsburg.de/~rauch/sane/sane-umax.html</A>
xsane: <A HREF="http://www.wolfsburg.de/~rauch/sane/sane-xsane.html">http://www.wolfsburg.de/~rauch/sane/sane-xsane.html</A>
E-Mail: mailto:<A HREF="mailto:Oliver.Rauch@Wolfsburg.DE?Subject=Re:%20quick%20note%20from%20the%20TWAIN/SANE%20meeting%20at%20OLS&In-Reply-To=&lt;3990452B.D8E9DA40@wolfsburg.de&gt;">Oliver.Rauch@Wolfsburg.DE</A>
<P><P><P>--
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?Subject=Re:%20quick%20note%20from%20the%20TWAIN/SANE%20meeting%20at%20OLS&In-Reply-To=&lt;3990452B.D8E9DA40@wolfsburg.de&gt;">majordomo@mostang.com</A>
</PRE>
<P><!-- body="end" -->
<HR NOSHADE>
<UL>
<!-- next="start" -->
<LI><STRONG>Next message:</STRONG> <A HREF="0076.html">Oliver Rauch: "xsane-win32-0.61 works on Windows NT"</A>
<LI><STRONG>Previous message:</STRONG> <A HREF="0074.html">Henning Meier-Geinitz: "Re: Are we ready for a new release?"</A>
<LI><STRONG>In reply to:</STRONG> <A HREF="0047.html">David Mosberger-Tang: "Re: quick note from the TWAIN/SANE meeting at OLS"</A>
<!-- nextthread="start" -->
<!-- reply="end" -->
<LI><STRONG>Messages sorted by:</STRONG>
<A HREF="date.html#75">[ date ]</A>
<A HREF="index.html#75">[ thread ]</A>
<A HREF="subject.html#75">[ subject ]</A>
<A HREF="author.html#75">[ author ]</A>
</UL>
<!-- trailer="footer" -->
<HR NOSHADE>
<P>
<SMALL>
<EM>
This archive was generated by <A HREF="http://www.hypermail.org/">hypermail 2b29</A>
: <EM>Tue Aug 08 2000 - 10:36:18 PDT</EM>
</EM>
</SMALL>
</BODY>
</HTML>