kopia lustrzana https://gitlab.com/sane-project/website
80 wiersze
4.3 KiB
HTML
80 wiersze
4.3 KiB
HTML
<!-- received="Tue Aug 3 14:04:14 1999 PDT" -->
|
|
<!-- sent="Tue, 03 Aug 1999 14:05:28 -0700" -->
|
|
<!-- name="Stephen Williams" -->
|
|
<!-- email="steve@icarus.com" -->
|
|
<!-- subject="Re: SANE_FRAME Formats (was Re: xsane-0.31 available)" -->
|
|
<!-- id="199908032105.OAA00432@icarus.com" -->
|
|
<!-- inreplyto="37A69A5C.3C815D75@gemse.fr" -->
|
|
<title>sane-devel: Re: SANE_FRAME Formats (was Re: xsane-0.31 available)</title>
|
|
<h1>Re: SANE_FRAME Formats (was Re: xsane-0.31 available)</h1>
|
|
<b>Stephen Williams</b> (<a href="mailto:steve@icarus.com"><i>steve@icarus.com</i></a>)<br>
|
|
<i>Tue, 03 Aug 1999 14:05:28 -0700</i>
|
|
<p>
|
|
<ul>
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#33">[ date ]</a><a href="index.html#33">[ thread ]</a><a href="subject.html#33">[ subject ]</a><a href="author.html#33">[ author ]</a>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0034.html">Oliver Rauch: "Re: RGBI (was Re: xsane-0.31 available)"</a>
|
|
<li> <b>Previous message:</b> <a href="0032.html">Nick Lamb: "Re: RGBI (was Re: xsane-0.31 available)"</a>
|
|
<li> <b>In reply to:</b> <a href="0019.html">Andreas Rick: "SANE_FRAME Formats (was Re: xsane-0.31 available)"</a>
|
|
<!-- nextthread="start" -->
|
|
<li> <b>Next in thread:</b> <a href="0036.html">Oliver Rauch: "Re: SANE_FRAME Formats (was Re: xsane-0.31 available)"</a>
|
|
<!-- reply="end" -->
|
|
</ul>
|
|
<!-- body="start" -->
|
|
<a href="mailto:rickand@gemse.fr">rickand@gemse.fr</a> said:<br>
|
|
<i>> The problem with defining all thinkable formats is that it adds a</i><br>
|
|
<i>> considerable amount of complexity to the frontend which is only used</i><br>
|
|
<i>> for one specific backend which is able to produce that one particular</i><br>
|
|
<i>> data-type. </i><br>
|
|
<p>
|
|
There should be some way for the frontend and backend to negotiate formats,<br>
|
|
and a small core set of formats that both must support. For example, if<br>
|
|
my scanner-with-compression driver is hooked to a frontend that knows<br>
|
|
of none of its high performance formats, then the driver, to be compliant,<br>
|
|
should be able to resort to RGB or somesuch.<br>
|
|
<p>
|
|
On the other hand, I will be able to write a nifty fastscan program that<br>
|
|
*does* know about SCAN_FRAME_JFIF and can do all the right things and<br>
|
|
can ask for the JFIF format from the scanner. Great!<br>
|
|
<p>
|
|
So, I think there must be a small set of "must have" frame formats,<br>
|
|
and a larger set of "standard optional" formats that handle some of<br>
|
|
the common and obvious formats, like JPEG. The negotiation process could<br>
|
|
also allow for a set of local or private formats that are outside any<br>
|
|
sort of standard definition.<br>
|
|
<p>
|
|
If all applications must support any combination of frame types, then<br>
|
|
the application writers will go nuts. If, on the other hand the scanner<br>
|
|
vendors must work with an excessively short list of formats, they will<br>
|
|
not be able to demonstrate the value of their nifty expensive equipment.<br>
|
|
<p>
|
|
Maybe there should be some standard option that the application can query<br>
|
|
to get a list of all the supported frame formats from the scanner. This<br>
|
|
would be sufficient, and allow new frame type to be added in the future<br>
|
|
without breaking compatibility.<br>
|
|
<pre>
|
|
--
|
|
Steve Williams "The woods are lovely, dark and deep.
|
|
<a href="mailto:steve@icarus.com">steve@icarus.com</a> But I have promises to keep,
|
|
<a href="mailto:steve@picturel.com">steve@picturel.com</a> and lines to code before I sleep,
|
|
<a href="http://www.picturel.com">http://www.picturel.com</a> And lines to code before I sleep."
|
|
<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="0034.html">Oliver Rauch: "Re: RGBI (was Re: xsane-0.31 available)"</a>
|
|
<li> <b>Previous message:</b> <a href="0032.html">Nick Lamb: "Re: RGBI (was Re: xsane-0.31 available)"</a>
|
|
<li> <b>In reply to:</b> <a href="0019.html">Andreas Rick: "SANE_FRAME Formats (was Re: xsane-0.31 available)"</a>
|
|
<!-- nextthread="start" -->
|
|
<li> <b>Next in thread:</b> <a href="0036.html">Oliver Rauch: "Re: SANE_FRAME Formats (was Re: xsane-0.31 available)"</a>
|
|
<!-- reply="end" -->
|
|
</ul>
|