Re: SANE & exposure times

Nick Lamb (njl98r@ecs.soton.ac.uk)
Thu, 29 Jul 1999 17:17:45 +0100 (GMT)

There is a third option which won't have me (or anyone else) crying out
for the lost precision from messing about with my data in the backend,
while avoiding having to put the same code in every frontend...

You can write "proxy" backends in SANE, like sane-net, which look like
both a front-end and a back-end. This means that Coolscan need only
know how to do standard SANE stuff (+ Exposures or whatever exported
as a SANE well-known-option) and the frontend need know nothing about
negatives, but the proxy will do any mangling for you.

This way users who want e.g. exciting multiple-scan mangling, or cool
exposure time compensation algorithms, can use them without everyone
having to put up with the overhead, delay, and/or loss of precision.

Isn't this the best of all possible worlds?

Nick.

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