Le Tuesday 08 July 2008 21:42:09 K?re S?rs, vous avez ?crit?:
Hi,
On Mondayen den 7 July 2008 23:51:24 m. allan noah wrote:
ok guys- take 4:
Six general points for sane 1.1.x:
- no changes to function calls
- no changes to structures
- 1.0 backends forward compatible with 1.1
On Wednesday 09 July 2008, m. allan noah wrote:
Is anybody updating the test backend with the new features? I needed to
add a gamma table stub to the test backend to be able to implement
gammatable support in libksane.
i dont recall seeing a patch from you for the gamma table support- did
Hi,
On Mondayen den 7 July 2008 23:51:24 m. allan noah wrote:
ok guys- take 4:
Six general points for sane 1.1.x:
- no changes to function calls
- no changes to structures
- 1.0 backends forward compatible with 1.1
- improve backend consistency
- support more advanced scanners
-
On 7/8/08, K?re S?rs kare.sars at kolumbus.fi wrote:
Hi,
On Mondayen den 7 July 2008 23:51:24 m. allan noah wrote:
ok guys- take 4:
Six general points for sane 1.1.x:
- no changes to function calls
- no changes to structures
- 1.0 backends forward compatible with 1.1
ok guys- take 4:
Six general points for sane 1.1.x:
- no changes to function calls
- no changes to structures
- 1.0 backends forward compatible with 1.1
- improve backend consistency
- support more advanced scanners
- improve cooperation with modern system services
Specific proposals:
1.
Hi,
or perhaps scan2 or altscan?
No ! you need to keep to semantic ! altscan or scan is not
selfexplanatory. Please prefer film or scan-film.
We should also state whether we should use _ or - in option name. I
guess that the standard is lowercase + hyphen + digit.
?tienne.
Hi,
some scanners even have simplex / duplex buttons or even fine grained
to up/down arrows to setup resolution, color mode etc. (i.g. the
popular HP 7400).
In the Avision backend I know use a string option to spit out
a message the program can parse.
Going with the current trend, maybe a xml
Hi Allan,
can you explain the paper width option to me? Why can we
not simply use br x/y?
Actually I got a Fujitsu scanner here and find the duplicate
paper width option annoying at best.
Aside the already mentioned button to use some more extend-able
XML encoding instead of a hardcoded set, I
On 5/26/08, ?tienne Bersac bersace03 at gmail.com wrote:
Hi,
or perhaps scan2 or altscan?
No ! you need to keep to semantic ! altscan or scan is not
selfexplanatory. Please prefer film or scan-film.
i doubt any frontend is going to code distinct support for such a
unique button, but we
On 5/26/08, Ren? Rebe rene at exactcode.de wrote:
Hi,
some scanners even have simplex / duplex buttons or even fine grained
to up/down arrows to setup resolution, color mode etc. (i.g. the
popular HP 7400).
right- but what is the frontend going to do with that, read the user's
setting,
sorry rene- this should have gone to list...
On 5/26/08, m. allan noah kitno455 at gmail.com wrote:
On 5/26/08, Ren? Rebe rene at exactcode.de wrote:
Hi Allan,
can you explain the paper width option to me? Why can we
not simply use br x/y?
Actually I got a Fujitsu scanner
Hi,
but what is the frontend going to do with that, read the user's
setting, then turn the data back around and set the resolution and
duplex options? it seems that would be better done in the backend
itself.?
But the frontend should be aware that the device has changed some value,
at least
On 5/26/08, ?tienne Bersac bersace03 at gmail.com wrote:
Hi,
but what is the frontend going to do with that, read the user's
setting, then turn the data back around and set the resolution and
duplex options? it seems that would be better done in the backend
itself.?
But the
Hi,
ps: this time to the list as well :-)
m. allan noah wrote:
On 5/26/08, Ren? Rebe rene at exactcode.de wrote:
Hi Allan,
can you explain the paper width option to me? Why can we
not simply use br x/y?
Actually I got a Fujitsu scanner here and find the duplicate
paper width option
On 5/26/08, Ren? Rebe rene at exactcode.de wrote:
Hi,
ps: this time to the list as well :-)
m. allan noah wrote:
On 5/26/08, Ren? Rebe rene at exactcode.de wrote:
Hi Allan,
can you explain the paper width option to me? Why can we
not simply use br x/y?
Actually I
El Wednesday 21 May 2008 20:50:46 m. allan noah escribi?:
5. Several new well-known options for buttons and sensors. Backends
should use the closest one to the meaning of the label on the scanner
or the button's use in the manufacturer's software. Backends may also
use a different name if no
or perhaps scan2 or altscan?
allan
On 5/25/08, JKD jkdsoft at gmail.com wrote:
El Wednesday 21 May 2008 20:50:46 m. allan noah escribi?:
5. Several new well-known options for buttons and sensors. Backends
should use the closest one to the meaning of the label on the scanner
or the
Hi,
From my point of view, everything is fine.
Regards,
?tienne.
ok guys- take 3:
Six general points for sane 1.1.x:
- no changes to function calls
- no changes to structures
- 1.0 backends forward compatible with 1.1
- improve backend consistency
- support more advanced scanners
- improve cooperation with modern system services
Specific proposals:
1.
Hi,
Maybe fax and copy too?
fax is good, but copy may be redundant with print, isn't it ?
The Canon LiDE 60 I have to hand has copy, scan, pdf, e-mail
buttons on the front
We should add pdf as well. e-mail should be renamed to mailto (or
vice versa).
Regards,
?tienne.
Then i will await your list of preferred button names :)
allan
On Fri, May 16, 2008 at 12:56 PM, ?tienne Bersac bersace03 at gmail.com wrote:
Hi,
5. One new SANE_TYPE value: HW_BUTTON (do we also need consistent names?)
Yes, well-known naming would be very nice. Fujitsu backend is fairly
Hi,
Agree, HW_BUTTON is redundant with HARD_SELECT. Sorry for not notifying
it earlier.
?tienne.
Hi,
Then i will await your list of preferred button names :)
I suggest :
* auto for blank/context dependant button.
* scan for start button
* cancel
* paper-in but what for multiple source device ? (maybe
autoselecting source is enough ?)
* mailto
On 16 May 2008, at 20:50, ?tienne Bersac wrote:
* auto for blank/context dependant button.
* scan for start button
* cancel
* paper-in but what for multiple source device ? (maybe
autoselecting source is enough ?)
* mailto
* print
Maybe fax and
Alessandro Zummo azummo-lists at towertech.it writes:
On Thu, 08 May 2008 09:29:09 +0900
Olaf Meeuwissen olaf.meeuwissen at avasys.jp wrote:
don't know yet. I still have to check epkowa code then Olaf and I could
maybe discuss the thing in order to have similar behaviours.
The
proprietary unices can't use gcc or another C99 compiler?
Which unix in particular?
Pretty much all of them ship compilers that do not implement C99 or
do
not implement all of it yet. Moreover, we're speaking of systems that
often do not get updated for a variety of reasons, so you
Alessandro Zummo azummo-lists at towertech.it writes:
On Wed, 07 May 2008 11:58:52 +0200
?tienne Bersac bersace03 at gmail.com wrote:
Hi,
So you mean an hardware selected option that can be read after the
scan ? Sounds good !
don't know yet. I still have to check epkowa code then Olaf
On Thu, 08 May 2008 09:29:09 +0900
Olaf Meeuwissen olaf.meeuwissen at avasys.jp wrote:
don't know yet. I still have to check epkowa code then Olaf and I could
maybe discuss the thing in order to have similar behaviours.
The information is returned as part of the status (see ESC f, FS F).
m. allan noah kitno455 at gmail.com wrote:
Hi,
still not sure how to document that requirement for the front-end
author, because those device names will vary quite a bit between
platforms...
Use the device name returned by the backend unless you know damn well
what you are doing.
There,
On Thu, 08 May 2008 13:56:45 +0200
Julien BLACHE jb at jblache.org wrote:
m. allan noah kitno455 at gmail.com wrote:
Hi,
still not sure how to document that requirement for the front-end
author, because those device names will vary quite a bit between
platforms...
Use the device
On 5/6/08, ?tienne Bersac bersace03 at gmail.com wrote:
Hi,
Thanks alan fo this post. I agree with everything on you list.
Just add
something : would it be possible to just ensure that all usb
scanner
backends support libusb:xxx:yyy as fallback device name ?
i think we can
On 5/8/08, Alessandro Zummo azummo-lists at towertech.it wrote:
On Thu, 08 May 2008 13:56:45 +0200
Julien BLACHE jb at jblache.org wrote:
m. allan noah kitno455 at gmail.com wrote:
Hi,
still not sure how to document that requirement for the front-end
author, because those
:) libusb is probably used in 90% of the user base..
shouldn't be a problem,
unless someone is really using a 2.4 kernel with /dev/scanner
typical linux developer response :) sane builds on alot of other
systems- e.g. the OSX libusb names are really long GUID-looking
things...
On Thu, 8 May 2008 08:24:37 -0400
m. allan noah kitno455 at gmail.com wrote:
:) libusb is probably used in 90% of the user base.. shouldn't be a
problem,
unless someone is really using a 2.4 kernel with /dev/scanner
typical linux developer response :) sane builds on alot of other
On Thu, 08 May 2008 14:19:38 +0200 CEST
Fran?ois Revol revol at free.fr wrote:
On 5/6/08,
IIRC some non-standard (linux specific) types were used (u_int8_t ?) in
place of standard ones, without even including the correct headers, so
I had to fix many backends.
That might not only affect
Alessandro Zummo azummo-lists at towertech.it wrote:
if there are standard and equivalent types, we should use them.
iirc some of them were added with C99. Given we are now
in 2008 we might start supporting C99 :-D
Will break proprietary Unices.
JB.
--
Julien BLACHE
On Thu, 08 May 2008 19:13:39 +0200
Julien BLACHE jb at jblache.org wrote:
Alessandro Zummo azummo-lists at towertech.it wrote:
if there are standard and equivalent types, we should use them.
iirc some of them were added with C99. Given we are now
in 2008 we might start supporting C99
Alessandro Zummo azummo-lists at towertech.it wrote:
proprietary unices can't use gcc or another C99 compiler?
Which unix in particular?
Pretty much all of them ship compilers that do not implement C99 or do
not implement all of it yet. Moreover, we're speaking of systems that
often do not
On Tue, 6 May 2008 16:25:02 -0400
m. allan noah kitno455 at gmail.com wrote:
We don't understand the problem space enough to write a proper schema.
If SANE_FRAME_XML goes in, it has to be flexible enough for new
backend authors to actually use it via their own schema, which can be
embedded in
Alessandro Zummo azummo-lists at towertech.it writes:
On Mon, 5 May 2008 13:56:58 -0400
m. allan noah kitno455 at gmail.com wrote:
2. Consistent well known-options, button handling and papersize come
to mind. others?
when I wrote epson2 i removed the paper size support that was in epson.
Alessandro Zummo azummo-lists at towertech.it writes:
On Mon, 5 May 2008 13:56:58 -0400
m. allan noah kitno455 at gmail.com wrote:
Other things from stef's list have been left out because the dont meet
my 5 points, anyone else have some more?
there are some patches that Julien included
m. allan noah kitno455 at gmail.com writes:
6. Common debugging bitmask:
1 major errors
2 minor errors
4 function start/stop msgs
8 function detail msg
16 SANE_OPTION processing msgs
32 calibration msgs
64 outgoing command dump
128 incoming data dump
help me fix that...
Please allow
On Wed, 07 May 2008 10:15:36 +0900
Olaf Meeuwissen olaf.meeuwissen at avasys.jp wrote:
Some of the EPSON models support hardware paper size detection. You'd
want at least an option to toggle whether or not you want to use it.
is that supported in epson/epkowa?
As for standard paper
Hello,
On May 6 08:08 Frank Zago wrote:
6. Common debugging bitmask:
1 major errors
2 minor errors
4 function start/stop msgs
8 function detail msg
16 SANE_OPTION processing msgs
32 calibration msgs
64 outgoing command dump
128 incoming data dump
help me fix that...
Alessandro Zummo azummo-lists at towertech.it writes:
On Wed, 07 May 2008 10:15:36 +0900
Olaf Meeuwissen olaf.meeuwissen at avasys.jp wrote:
Some of the EPSON models support hardware paper size detection. You'd
want at least an option to toggle whether or not you want to use it.
is
On Wed, 07 May 2008 11:48:18 +0200
?tienne Bersac bersace03 at gmail.com wrote:
Hi,
Please avoid using paper name and rather keep using paper lengths and
let frontend use papernames on top of that. This allow frontend to use
custom paper sizes (without specifying top left corner coordinate)
Hi,
So you mean an hardware selected option that can be read after the
scan ? Sounds good !
Regards,
?tienne.
On Wed, 07 May 2008 11:58:52 +0200
?tienne Bersac bersace03 at gmail.com wrote:
Hi,
So you mean an hardware selected option that can be read after the
scan ? Sounds good !
don't know yet. I still have to check epkowa code then Olaf and I could
maybe discuss the thing in order to have
Olaf Meeuwissen olaf.meeuwissen at avasys.jp wrote:
Hi,
there are some patches that Julien included in its debian
package that might be useful. I especially like the one
that searches for config files in /etc/sane.d/dll.d
+1
Due to popular demand, I've now committed that patch in the
Hi,
Thanks alan fo this post. I agree with everything on you list. Just add
something : would it be possible to just ensure that all usb scanner
backends support libusb:xxx:yyy as fallback device name ?
Regards,
?tienne.
This is a much better solution than coming with a completely new SANE2
API. At the Linux Foundation Summit in April we have decided on taking
the SANE1 API into LSB 4.0, so that scanner manufacturers can make
distribution-independent LSB-based scanner driver packages.
Standardizing on the
6. Common debugging bitmask:
1 major errors
2 minor errors
4 function start/stop msgs
8 function detail msg
16 SANE_OPTION processing msgs
32 calibration msgs
64 outgoing command dump
128 incoming data dump
help me fix that...
Should these need to be bitmasks ? I think most
6. Common debugging bitmask:
1 major errors
2 minor errors
4 function start/stop msgs
8 function detail msg
16 SANE_OPTION processing msgs
32 calibration msgs
64 outgoing command dump
128 incoming data dump
help me fix that...
Should these need to be bitmasks ? I think most
we can stick with levels, if we make them more consistent. I
personally am a fan of bitmasks, because of the flexibility, but you
are correct that most users will have trouble doing the bitwise AND :)
allan
On Tue, May 6, 2008 at 9:08 AM, Frank Zago sane at zago.net wrote:
6. Common
m. allan noah kitno455 at gmail.com wrote:
Hi,
there are some patches that Julien included in its debian
package that might be useful. I especially like the one
that searches for config files in /etc/sane.d/dll.d
That's the only one that can be integrated into SANE upstream,
Alessandro Zummo azummo-lists at towertech.it wrote:
Hi,
shall xml be a free type or shall we define its tags?
I dont know. that is why i originally left it out of 1.1.0, until some
upstart came along and forced my hand :) seriously, i think we should
leave it undefined for now, and
m. allan noah kitno455 at gmail.com wrote:
Hi,
we can stick with levels, if we make them more consistent. I
personally am a fan of bitmasks, because of the flexibility, but you
are correct that most users will have trouble doing the bitwise AND :)
I vote for bitmasks too:
- debug stuff is
How about we just state that the schema is backend dependent?
allan
On Tue, May 6, 2008 at 1:24 PM, Julien BLACHE jb at jblache.org wrote:
Alessandro Zummo azummo-lists at towertech.it wrote:
that was the only part with a spec, the whole dtd/document/page model
yet has to
On Tue, 6 May 2008 16:10:37 -0400
m. allan noah kitno455 at gmail.com wrote:
How about we just state that the schema is backend dependent?
pretty difficult if you want to parse the results.. it makes sense
to have some common output.
--
Best regards,
Alessandro Zummo,
Tower
We don't understand the problem space enough to write a proper schema.
If SANE_FRAME_XML goes in, it has to be flexible enough for new
backend authors to actually use it via their own schema, which can be
embedded in the stream.
allan
On Tue, May 6, 2008 at 4:13 PM, Alessandro Zummo
azummo-lists
m. allan noah kitno455 at gmail.com wrote:
Hi,
How about we just state that the schema is backend dependent?
Could depend on the model, too ;)
As I see it, the XML frame type will be transformed by the frontend by
applying an XSLT stylesheet before using the data.
That means adding support
Lets talk about SANE 1.1.0 release, both timetables and deliverables.
I have tried to pick some things from recent discussions, and build on
the momentum provided by stef and julien. It is not my intention to
hijack this process, but I have some spare cycles coming up, and we
are all tired of
On Mon, 5 May 2008 13:56:58 -0400
m. allan noah kitno455 at gmail.com wrote:
3. Two new return codes: SANE_STATUS_HW_LOCK to tell the frontend that the
scanner has a hardware lock installed, and SANE_STATUS_WARMING_UP for lamp.
it would be fine if we can keep those in sync with sane
Hello,
I think this is a reasonable plan, and I feel like working on it.
Regards,
Stef
On Mon, May 5, 2008 at 2:06 PM, Alessandro Zummo
azummo-lists at towertech.it wrote:
On Mon, 5 May 2008 13:56:58 -0400
m. allan noah kitno455 at gmail.com wrote:
3. Two new return codes: SANE_STATUS_HW_LOCK to tell the frontend that the
scanner has a hardware lock installed, and
On Mon, 5 May 2008 14:38:34 -0400
m. allan noah kitno455 at gmail.com wrote:
On Mon, May 5, 2008 at 2:06 PM, Alessandro Zummo
azummo-lists at towertech.it wrote:
On Mon, 5 May 2008 13:56:58 -0400
m. allan noah kitno455 at gmail.com wrote:
3. Two new return codes: SANE_STATUS_HW_LOCK
On Mon, 5 May 2008 13:56:58 -0400
m. allan noah kitno455 at gmail.com wrote:
Other things from stef's list have been left out because the dont meet
my 5 points, anyone else have some more?
there are some patches that Julien included in its debian
package that might be useful. I especially
On Mon, 5 May 2008 13:56:58 -0400
m. allan noah kitno455 at gmail.com wrote:
2. Consistent well known-options, button handling and papersize come
to mind. others?
when I wrote epson2 i removed the paper size support that was in epson.
I believe the paper size is something better suited for
Alessandro Zummo azummo-lists at towertech.it wrote:
Hi,
there are some patches that Julien included in its debian
package that might be useful. I especially like the one
that searches for config files in /etc/sane.d/dll.d
That's the only one that can be integrated into SANE upstream,
On Mon, May 5, 2008 at 3:54 PM, Alessandro Zummo
azummo-lists at towertech.it wrote:
On Mon, 5 May 2008 13:56:58 -0400
m. allan noah kitno455 at gmail.com wrote:
2. Consistent well known-options, button handling and papersize come
to mind. others?
when I wrote epson2 i removed the
On Mon, May 5, 2008 at 3:51 PM, Julien BLACHE jb at jblache.org wrote:
Alessandro Zummo azummo-lists at towertech.it wrote:
Hi,
there are some patches that Julien included in its debian
package that might be useful. I especially like the one
that searches for config files in
71 matches
Mail list logo
