[sane-devel] SANE frozen in amber ?
Alessandro Zummo
azummo-lists at towertech.it
Thu Jun 11 19:11:49 UTC 2009
On Thu, 11 Jun 2009 15:08:28 -0400
"m. allan noah" <kitno455 at gmail.com> wrote:
> >
> > a backend might choice to implement it or not. such an info is
> > useful but shouldn't be mandatory.
>
> bah- then no front-end will use it, since it is not guaranteed to be
> there. So, they will still cache the data from sane_find_scanners,
> effectively increasing the amount of code on both sides of the API.
>
> Variability of backends (particularly in option handling) is by far
> the biggest impediment to using sane, and I would prefer that we
> improved the situation, rather than exacerbated it.
I believe that by forcing a minimum level and allowing some degree
of freedom you'll have the maximum chance of having backends ported
to the newest version of teh API.
Some degree doesn't mean something like OpenGL, where you have a
terrible mess.
An application can simply tell the user that no maker/model information
is available. sooner or later the backend will be updated.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
More information about the sane-devel
mailing list