On 10.04.2008, at 21:33, stef wrote:
> Le Wednesday 09 April 2008 21:38:26, vous avez ?crit :
>>
>> You are still just arguing around the dancing cow here.
>>
>> With a potentially new sane_end whatever function you still would
>> have
>> to
>> keep track where the head is. A frontend may still
Le Wednesday 09 April 2008 21:38:26, vous avez ?crit?:
>
> You are still just arguing around the dancing cow here.
>
> With a potentially new sane_end whatever function you still would have
> to
> keep track where the head is. A frontend may still read less data and in
> any case you would need to
Hi,
On 09.04.2008, at 21:27, stef wrote:
> Le Wednesday 09 April 2008 12:48:22 Ren? Rebe, vous avez ?crit :
>
>>
>> As the backend controls the device and reads the image data somehow,
>> it should have knowledge about the actual head position and should be
>> able to perform the required actions
Le Wednesday 09 April 2008 12:48:22 Ren? Rebe, vous avez ?crit?:
>
> As the backend controls the device and reads the image data somehow,
> it should have knowledge about the actual head position and should be
> able to perform the required actions even with the current interface.
>
> Where exactl
Hi,
stef wrote:
> Le Sunday 06 April 2008 21:16:44 m. allan noah, vous avez ?crit :
>> On 3/28/08, Rene Rebe wrote:
> But before starting, there are some things I'd like to see in
> the
>>> new standard:
> - the current code flow is
> sane_init
>
Le Sunday 06 April 2008 21:16:44 m. allan noah, vous avez ?crit?:
> On 3/28/08, Rene Rebe wrote:
> > > > But before starting, there are some things I'd like to see in
> > > > the
> >
> > new standard:
> > > > - the current code flow is
> > > > sane_init
> > > > sane
On 3/28/08, Rene Rebe wrote:
> > > But before starting, there are some things I'd like to see in the
> new standard:
> > > - the current code flow is
> > > sane_init
> > > sane_open
> > > sane_start
> > > sane_read
Johannes Meixner wrote:
Hi,
> I think I understand now what the difference is between
> cupsd/saned and hpiod/libhpmud:
>
> cupsd and saned provide a driver and frontend independent
> single central service to do printing and scanning.
Exactly.
> In contrast the hpiod was an additional special
Hello,
On Apr 1 18:00 Emmanuel Fust wrote (shortened):
> That's the point: CUPSD is a daemon regardless of implementation
> of the backend, daemon or I/O-lib. Nothing talk or invoke directly
> this io backend all talk to CUPSD via tcp or domain-unix socket
> in case of printing. It should be the
Johannes Meixner wrote:
Hi,
> The CUPS backend runs only as long as one particular print job
> is sent to the device, then it finishes.
Same for saned.
> But how to deal with a user who runs a frontend to scan
> multiple sheets on a all-in-one device and in between
> a (longer) print job comes
> Message du 01/04/08 15:03
> De : "Johannes Meixner"
> A : sane-devel at lists.alioth.debian.org
> Copie ? :
> Objet : Re: [sane-devel] SANE2 standard completion
>
>
> Hello,
>
> On Mar 28 18:40 Julien BLACHE wrote (shortened):
> > ... I think i
Hello,
On Mar 28 19:13 Julien BLACHE wrote (shortened):
> ... provide a central point (saned) handling the hardware
> entirely,
...
> Something much more simple than CUPS, but yeah, basically.
...
> Oh, I forgot to add: we get real locking/device management
> that way, too.
It may get complicate
Hello,
On Mar 28 18:40 Julien BLACHE wrote (shortened):
> ... I think it'd really be better to have the
> frontends be entirely isolated from the backends, as I explained
> already.
>
> This would provide a central point (saned) handling the hardware
> entirely
To avoid confusion with the cupsd
Hi,
> Now tell me, how do you transparently share scanners from one box to
> another without a daemon?
I never said that. I said ? how to avoid running service if there is no
scanner plugged ? ?. I even implemented a daemon for polling sensor.
Please reread past mail rather than putting words in
"m. allan noah" wrote:
Hi,
> As such, i would like to extend SANE1 just a little bit, and i dont
> care if we call it SANE2 and give it a new soversion. Then, we can
> spend all the time you guys want developing an extensible network
> protocol, and turning saned into a real full-time daemon, be
?tienne Bersac wrote:
Hi,
>> I also quite like the "users don't want another daemon running"
>
> Personnaly, i don't care to have a cups for scanner. But people in
> distributions, dev in other pieces of the stacks and end-users tell so.
You're getting more and more funny as time passes. Let's
Hi,
> GUI clients are probably the largest group of _users_ of SANE. CLI
> clients probably aquire more _images_. The needs of both groups must
> be met.
Completely agree.
Best regards,
?tienne.
Hi,
> I also quite like the "users don't want another daemon running"
Personnaly, i don't care to have a cups for scanner. But people in
distributions, dev in other pieces of the stacks and end-users tell so.
Again, we should not impose a service but rather keep at least library
(and the daemon a
Hi,
> especially if you are going to go blogging about us behind our backs :)
Do you mean i have to post each blog post about SANE here ;)
?tienne.
On 3/31/08, ?tienne Bersac wrote:
> Hi,
>
>
> > I also quite like the "users don't want another daemon running"
>
>
> Personnaly, i don't care to have a cups for scanner. But people in
> distributions, dev in other pieces of the stacks and end-users tell so.
> Again, we should not impose a serv
OOooppss, I was a bit late and it is described in a better English than mine.
+10
EF.
> Message du 28/03/08 19:09
> De : "Julien BLACHE"
>
> Based on the current saned, it can already be achieved:
> - link saned statically to libsane-dll (what we know as libsane
>today)
> - ship libsane-
> Message du 28/03/08 22:50
> De : "Julien BLACHE"
> "m. allan noah" wrote:
>
> Hi,
>
> >> - scanner's button handling
> >
> > this is overly complicated, and should be re-examined.
>
> For that and other reasons, I think it'd really be better to have the
> frontends be entirely isolated f
On 3/30/08, Emmanuel Fust wrote:
> > Message du 28/03/08 22:50
> > De : "Julien BLACHE"
> > "m. allan noah" wrote:
> >
> > Hi,
> >
> > >> - scanner's button handling
> > >
> > > this is overly complicated, and should be re-examined.
> >
> > For that and other reasons, I think it'd really be better
?tienne Bersac wrote:
> By talking about HAL, i mean do not impose another system service and
> let external project do it on top of SANE, be it either a DBus daemon, a
> HAL addon, a regular daemon, etc.
Bar telling "no new service please, HAL can launch things as needed".
Yeah, that's it.
I
Rene Rebe wrote:
> The TWAIN standard is open, and here is the link:
>
> http://twain.org/docs/TWAIN19.pdf
Back in the days, ISTR it wasn't open. I'll try to find some time to
go through it.
> Actually the capabilities are even quite similar.
That's what makes the most sense I think, so it's
On 28.03.2008, at 19:34, m. allan noah wrote:
> On Fri, Mar 28, 2008 at 2:28 PM, Rene Rebe wrote:
>>
>>
>> On 28.03.2008, at 19:19, m. allan noah wrote:
>>
>>
>>> On Fri, Mar 28, 2008 at 2:14 PM, Rene Rebe
>>> wrote:
>>>
On 28.03.2008, at 19:02, Alessandro Zummo wrote:
>>>
Hi,
> Could you PLEASE stop thinking "HAL" all the time?
Could you please stop taking HAL as an offense all the time ?
By talking about HAL, i mean do not impose another system service and
let external project do it on top of SANE, be it either a DBus daemon, a
HAL addon, a regular daemon, etc.
On 28.03.2008, at 19:19, m. allan noah wrote:
> On Fri, Mar 28, 2008 at 2:14 PM, Rene Rebe wrote:
>>
>> On 28.03.2008, at 19:02, Alessandro Zummo wrote:
>>
>>> On Fri, 28 Mar 2008 15:49:17 +0100
>>> Rene Rebe wrote:
>>>
Right now the only thing I miss are marks for infra-red frames, a
Hi,
On 28.03.2008, at 19:13, Julien BLACHE wrote:
> Rene Rebe wrote:
>
> Hi,
>
>> Sounds a bit Data Source Manager like-ish (in TWAIN terms), definetly
>> and idea for desktops.
>
> Yes. From what you told about TWAIN the other day, I think I like the
> architecture. I don't know enough about TW
Hi,
On 28.03.2008, at 19:09, Julien BLACHE wrote:
> ?tienne Bersac wrote:
>
> Hi,
>
>> Do you mean having some cups for scanner ?
>
> Something much more simple than CUPS, but yeah, basically.
>
>> Actually, i wish not, because users don't want another service. HAL
>> can
>> launch addon per d
On 28.03.2008, at 19:02, Alessandro Zummo wrote:
> On Fri, 28 Mar 2008 15:49:17 +0100
> Rene Rebe wrote:
>
>>
>> Right now the only thing I miss are marks for infra-red frames, and
>> maybe
>> a ability to pass duplex data without buffering the rear side, which
>> becomes
>> even more of a probl
Rene Rebe wrote:
Hi,
> Sounds a bit Data Source Manager like-ish (in TWAIN terms), definetly
> and idea for desktops.
Yes. From what you told about TWAIN the other day, I think I like the
architecture. I don't know enough about TWAIN to tell for sure,
though.
Oh, I forgot to add: we get real
?tienne Bersac wrote:
Hi,
> Do you mean having some cups for scanner ?
Something much more simple than CUPS, but yeah, basically.
> Actually, i wish not, because users don't want another service. HAL can
> launch addon per device which allow to launch nothing if no scanner
> present.
Could yo
On Fri, 28 Mar 2008 15:49:17 +0100
Rene Rebe wrote:
>
> Right now the only thing I miss are marks for infra-red frames, and
> maybe
> a ability to pass duplex data without buffering the rear side, which
> becomes
> even more of a problem with the next generation, higher end devices I
> got
Hi,
> This would provide a central point (saned) handling the hardware
> entirely, it can chat with other things (HAL, anything over D-Bus, you
> name it) and we totally avoid the current side effects we have today.
Do you mean having some cups for scanner ?
Actually, i wish not, because users d
Hi,
On 28.03.2008, at 18:40, Julien BLACHE wrote:
> "m. allan noah" wrote:
>
> Hi,
>
>>>- scanner's button handling
>>
>> this is overly complicated, and should be re-examined.
>
> For that and other reasons, I think it'd really be better to have the
> frontends be entirely isolated from
Hi,
On 28.03.2008, at 18:40, Oliver Rauch wrote:
> I can not believe it.
>
> There is someone who says I will start working on SANE2 and you have
> nothing better to do than to tell him it is better not to do it.
I did not tell him not to, but expressed my disbelieve in the whole
rewrite
"ever
"m. allan noah" wrote:
Hi,
>> - scanner's button handling
>
> this is overly complicated, and should be re-examined.
For that and other reasons, I think it'd really be better to have the
frontends be entirely isolated from the backends, as I explained
already.
This would provide a cent
I can not believe it.
There is someone who says I will start working on SANE2 and you have
nothing better to do than to tell him it is better not to do it.
This is called progress. Really good.
Best regards
Oliver
Am Freitag, den 28.03.2008, 08:52 +0100 schrieb Rene Rebe:
> Have you counted t
Hi Allan,
On 28.03.2008, at 14:46, m. allan noah wrote:
> On Thu, Mar 27, 2008 at 1:22 PM, stef wrote:
>>Hello,
>>
>>before any work can start on SANE 2, the current proposal
>> has to be completed.
>
> and before we can complete it, we must acknowlege that it has not been
> to
On 3/28/08, Julien BLACHE wrote:
> ?tienne Bersac wrote:
>
>
> > By talking about HAL, i mean do not impose another system service and
> > let external project do it on top of SANE, be it either a DBus daemon, a
> > HAL addon, a regular daemon, etc.
>
>
> Bar telling "no new service please, HAL
On Fri, Mar 28, 2008 at 2:28 PM, Rene Rebe wrote:
>
>
> On 28.03.2008, at 19:19, m. allan noah wrote:
>
>
> > On Fri, Mar 28, 2008 at 2:14 PM, Rene Rebe wrote:
> >
> > >
> > > On 28.03.2008, at 19:02, Alessandro Zummo wrote:
> > >
> > >
> > > > On Fri, 28 Mar 2008 15:49:17 +0100
> > > > Rene Reb
On Fri, Mar 28, 2008 at 2:14 PM, Rene Rebe wrote:
>
> On 28.03.2008, at 19:02, Alessandro Zummo wrote:
>
> > On Fri, 28 Mar 2008 15:49:17 +0100
> > Rene Rebe wrote:
> >
> >>
> >> Right now the only thing I miss are marks for infra-red frames, and
> >> maybe
> >> a ability to pass duplex d
On Thu, Mar 27, 2008 at 1:22 PM, stef wrote:
> Hello,
>
> before any work can start on SANE 2, the current proposal has to be
> completed.
and before we can complete it, we must acknowlege that it has not been
touched in 5 years, and many of its contributors are no longer active,
Hi,
On 28.03.2008, at 09:16, Alessandro Zummo wrote:
> On Fri, 28 Mar 2008 08:52:51 +0100
> Rene Rebe wrote:
>
>> Have you counted thru how many developers are willing to rewrite
>> their code (backends, frontends, etc.) for this arbitrarily defined
>> SANE
>> 2 "thing" ?
>>
>> My votes still
On Fri, 28 Mar 2008 08:52:51 +0100
Rene Rebe wrote:
> Have you counted thru how many developers are willing to rewrite
> their code (backends, frontends, etc.) for this arbitrarily defined SANE
> 2 "thing" ?
>
> My votes still are: preferably compatibly change SANE 1 or adopt
> TWAIN for Linux.
Have you counted thru how many developers are willing to rewrite
their code (backends, frontends, etc.) for this arbitrarily defined SANE
2 "thing" ?
My votes still are: preferably compatibly change SANE 1 or adopt
TWAIN for Linux.
On 27.03.2008, at 18:22, stef wrote:
> Hello,
>
> be
Hello,
before any work can start on SANE 2, the current proposal has to be
completed.
The major change is the image data format. SANE 2 will be able to
handle new formats easily (which matches the current needs, especially
regarding ir
channel). There will be 2 major
48 matches
Mail list logo
