On 6 April 2012 09:35, martin f krafft <madd...@debian.org> wrote: > I do wonder why you have all these backends, instead of just one. > What's the benefit? Wouldn't it be better to have one backend and > polish that until it glistens?
It all started off with scanimage, but the trouble with it is that there is no way of knowing which options affect other options, and therefore require the options to be reloaded. Some common ones are hardcoded - i.e. mode. Also, it is very slow - which I tried to fix with caching. libsane-perl is supposed to be the answer - perl binding to the sane protocol mean that the options can be reloaded when necessary, and it is fast - and nothing has to be hardcoded - and so I can expose every options that any backend offers - which differ from backend to backend. The answer to your problem of large number of options might be to select in Edit/Preferences which to be exposed. I could also expose all of them with the other frontends - but then there'd be no way of knowing when a reload would be necessary - so for the other frontends, an extra switch would have to specify whether to reload or not. So - I am slowly trying to polish libsane-perl. Profiles are on my todo list. But until it works for everybody, I'll carry on offering the others. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
