The actual wrapper around the packet is what isn't documented. It shows what
data is transmitted but nothing else. For example, I assume the format is
probably something like:
<packet id byte><..data bytes..>
If I don't have to look through the code to find this, I'll be happy:)
>For an actual implementation reference, see :
>
>sanei/sanei_codec_ascii.c
>sanei/sanei_codec_bin.c
>sanei/sanei_net.c
>sanei/sanei_wire.c
>backend/net.c
>frontend/saned.c
>
>This should provide you with quite enough reference and a bunch of
convenience
>functions to access the sane net protocol.
Truthfully I'd rather reverse engineer the protocol than figure it out via
the code. I've looked through it some and have followed the data flow, but
that's about as far as I'm going.
>Actually what you need to do, is to rewrite backend/net.c in a way that
>it exports a TWAIN interface, or write a SANE->TWAIN bridge interface
>that is simply linked to net.c.
Basically, I'll just write a C++ SANE wrapper around the network protocol
and implement the TWAIN DLL with it. I'll initially probably test the SANE
wrapper with a simple Win32 program that dumps 24bit Bitmap files given a
size and offset to scan with. Then when I get a chance I'll write the TWAIN
DLL.
Brian Macy
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com