Hi,
On Sun, Dec 08, 2002 at 05:51:17PM +0100, abel deuring wrote:
> >I hope It won't take too long to finish the core points of SANE2.
>
> Sounds promising.
Proposals/corrections/comments welcome :-)
> >SCSI reference manual for a scanner? Haha. Never seen such a beast.
> >Either it's labeled "
This is a multi-part message in MIME format.
--040005050005000808080300
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Henning Meier-Geinitz wrote:
>>Well, there is indeed not urgent need to change the interface for Sane1.
>>But there were a
Hi,
On Sun, Dec 08, 2002 at 04:15:56PM +0100, abel deuring wrote:
> >I would just switch to the new API in SANE2 and use e.g.
> >sanei_scsi_open (not sanei2_). All backends must be rewritten anyway.
> >So you avoid confusion if it's necessary to add a sanei_scsi_open2 in
> >future.
>
> Well, ther
Henning Meier-Geinitz wrote:
> Hi,
>
> On Sat, Dec 07, 2002 at 11:29:20PM +0100, abel deuring wrote:
>
>>Some time ago, I made some remarks on this list about things I don't
>>like in the sanei_scsi interface:
>>http://www.mostang.com/pipermail/sane-devel/2002-January/001463.html
>>Here is a pr
Hi,
On Sat, Dec 07, 2002 at 11:29:20PM +0100, abel deuring wrote:
> Some time ago, I made some remarks on this list about things I don't
> like in the sanei_scsi interface:
> http://www.mostang.com/pipermail/sane-devel/2002-January/001463.html
> Here is a proposal for a modified interface. The m
This is a multi-part message in MIME format.
--010608090107060104040506
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Some time ago, I made some remarks on this list about things I don't
like in the sanei_scsi interface:
http://www.mostang
