[sane-devel] Sane API Suggestion
Major A schrieb: The SANE API is designed to be simple and portable, and any change towards object orientation or functional programming would only bloat it unnecessarily. Sorry, if you want to interface Scheme to SANE, you'll have to adapt to the way things are. Well, changing the current API is indeed not a good idea. For newer versions, we should be a bit more open, IMHO. Adding a callback data argument to both sane_init() and SANE_Authorization_Callback would cause a number of problems, in particular that of network transparency. Scheme or C++ programmers would certainly like to use that parameter as a pointer to a structure, but that only works if the size of the argument is at least that of void*. Since the latter varies across platforms, this would be ugly and non-portable. I don't think that network transparency introduces a problem for user data pointer sizes. Since Sane itself does not deal with this pointer, the net backend does not need to send and receive the correct value of this pointer to/from the Sane server. Instead, the net backend can use the pointer value as passed by the application in the callback. Since the only callback in SANE is the one responsible for authentication, I'd say it wouldn't be worth changing anything. A Scheme frontend would either have to relay the authentication request to the user, in which case the callback data is not used, or look up username and password in a database, in which case the resource string supplied is sufficient. Well, some time has passed sine my last look into the Sane 2 API docs, but IIRC it has at least one more callback. Abel
[sane-devel] detect the correct scanner
i have a genius color page vivid-III but when mandrake detect it as a plustek, that has the same chip. Is this important or not? and how i can get it detected as genius color page vivid-III. ___ Yahoo! Messenger - Nueva versión GRATIS Super Webcam, voz, caritas animadas, y más... http://messenger.yahoo.es
[sane-devel] detect the correct scanner
Hi, On Tue, Jul 22, 2003 at 09:54:45PM +0200, Foffy wrote: i have a genius color page vivid-III but when mandrake detect it as a plustek, that has the same chip. Is this important or not? and how i can get it detected as genius color page vivid-III. It would have been important if the Plustek 1212U had been supported. But as far as I know this is not the case. The scanner search engine says: All devices using product ID 0x0001 are not supported, for others see Plustek backend. The older models seem to use a P98003 parallel port ASIC and a GenesysLogic parport-over USB brigde. The P98003 is also used by the P12 and PT12 models. So basically you need someone who writes a backend for that combination of chips. If you want to start coding yourself, have a look at http://www.meier-geinitz.de/sane/misc/unsupported.html. Bye, Henning
[sane-devel] Does anyone need help writing a backend?
Ah sorry Henning but i haven't got MS Windows. The main reason I moved to Linux was because I was fed up with dodgy windows installations, crashes, etc and did not want to give Mr Gates any money in order to rectify it. Red hat has been fine ever since I installed it, I just didn't realise that the 4500 wasn't supported. Regards, Stu On Tue, 2003-07-22 at 18:19, Henning Meier-Geinitz wrote: Hi, On Mon, Jul 21, 2003 at 10:21:11PM +0100, Stuart Hirons wrote: I have a UMAX 4500 sitting on my desk lying unused since I moved to Red Hat 4 months ago, can I be of any help here in obtaining any logs or anything ? If you have MS Windows installed, you could install usbsnoopy and get a log of a simple scan if that's possible. E.g. 1 cm x 1 cm in 100 dpi grayscale. I'll do that anyway once I have that scanner but if you do it now we may understand the protocoll a bit earlier :-) Bye, Henning ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel -- Stuart Hirons stu...@beandog.freeserve.co.uk
[sane-devel] detect the correct scanner
Hi Foffy_69, Assuming your scanner works, why do you care? Another solution to your problem would be to print a Plustek sticker and put it on top of the Genius logo. :) Frank. Foffy wrote: i have a genius color page vivid-III but when mandrake detect it as a plustek, that has the same chip. Is this important or not? and how i can get it detected as genius color page vivid-III.
[sane-devel] sane-backends effectively GPL'd in disguise?
Hi Olaf, IANAL but I'll try to answer anyway. None of these contain code. Just prototype and APIs. I don't think that the omission of the SANE exception would propagate to the rest of the code. Besides the README states that the backends are under GPL+exception. It is also quite clear that the authors of these files didn't intend to put these files under GPL only since they were written specifically for SANE. The files should be fixed though. Frank. Olaf Meeuwissen wrote: Dear all, I have been upgrading Image Scan! for Linux to use SANE internals from sane-backends-1.0.12. Ever since the FSF slapped us on the wrist for an unintentional violation of the GPL, we have a little allergic to license issues so I combed through the include/, lib/ and sanei/ directories for license problems. The following files in include/ and sanei/ are GPL'd *without* the SANE exception: include/lalloca.h include/lassert.h include/sane/sanei.h include/sane/sanei_codec_ascii.h include/sane/sanei_codec_bin.h include/sane/sanei_scsi.h include/sane/sanei_thread.h include/sane/sanei_usb.h include/sane/sanei_wire.h include/sane/saneopts.h sanei/linux_sg3_err.h Even though I have read the GPL twenty+ times over, I am still not sure whether this means that files including any of these would effectively void their SANE exception (assuming they have one). After all the SANE exception explicitly states: This exception does not, however, invalidate any other reasons why the executable file might be covered by the GNU General Public License. Ergo, files like sanei/sanei_scsi.c and sanei/sanei_usb.c, which include their counterpart header files, might in effect be released under the GPL and the GPL only without any SANE exception. The same logic applies to backends including files from the above list. The TODO notes that the getopt*.c and md5.c files have been checked for (and replaced by LGPL'd versions) precisely the reasons cited above. Could anyone shed any light on this?
