[sane-devel] SANE2 commitment
Alessandro Zummo wrote: Hello developers, since there seems to be interest in developing sane2, I've decided to start this thread in order to collect the commitment of each developer. I'm willing to port the epson driver to sane2, help porting the coolscan driver and handle the command line frontend. I think Giuseppe Sacco has showed interest to do coolscan bits. A friend of mine, Stefano Merlo, has committed himself to the canon driver. I'd appreciate if everyone who is interested can reply with their own commitments for the 2007.. ehm.. sane2 :) Firstly, kudos to Alessandro for starting a new attempt to get Sane2 going. Let's make sure that we don't get again an ugly exchange of arguments like we had, ummm, seven (?) years ago, which eventually froze the first attempt of a new version of Sane. Unfortunately, I can't make at present an honest commitment for contributions to Sane2 in the next year -- it is quite unclear how much time I will have. If I find time, I will work on the Sharp backend, on the sanei_scsi library (well, mostly it's Linux part... I don't know enough about the other platforms supported by Sane) and a Python library for Sane. I agree with Martin and Etienne that device detection and desktop integration should be improved, but I also think that we should keep support for operating systems that don't have any HAL support. My problem is that I don't know anything about HAL implementation in Linux or elsewhere -- can anybody give me a pointer to an introduction? Abel
[sane-devel] SANE2 commitment
Hi Martin, Il giorno dom, 17/12/2006 alle 19.52 +, Martin Owens ha scritto: [...] For device detection and management use HAL, update hal dbus code with all existing detection and status code which will keep these devices happy, enable the modification of the hal xml as a simple way of keeping track of which scanners work with which backends too, removing this from the backend code is a must. You can then change your clients to use hal and simply call dbus commands to scan etc. [...] That would be really nice. I wonder if this will only work on linux. What about *BSD, Solaris and Windows? Bye, Giuseppe
[sane-devel] SANE2 commitment
You can then change your clients to use hal and simply call dbus commands to scan etc. [...] That would be really nice. I wonder if this will only work on linux. What about *BSD, Solaris and Windows? I don't know about solaris, I know hal is being used in a number of linux distributions but not even all of them. windows has it's own hal and less is known about it. It might end up being a separate project for integrating sane with hal in order to repackage sane for certain linux distributions that can take advantage of newer device systems. Bye, Giuseppe Best Regards, Martin
[sane-devel] SANE2 commitment
hi all, I'm working on Gnome Scan and intend to be very active in this realm in the next year. This may hurt some people here. I want to bring scan support to hal. I intended to talk with sane people in january. I want in Gnome to use sane for access, not probe/detection. That's bad to probe each time you launch the app. I wonder if we need a kind of cups for scanner that use sane to access, receive job request and return stream of pictures. I wonder how to handle local and networked detection. I want to add avahi feature to scanner share. Likely, SANE 2 offer a new sane_open () prototype that allow to get device description without doing the probe. But how can hal know the sane device name ? I would like to add a scanner.sane.name field or similar into hal scanner device in order to allow app to use directly SANE (basically, a scaner cups will do that). Is this possible with SANE 1 ? If not, how does SANE 2 help for that ? Some of you may be attached to the double work of sane : device support, device probe. But i really think SANE must add a way for developer to handle device detection according to the target system standard (e.g. hal, windows, Solaris, etc.). I do not want sane to drop sane_get_devices (). Would be nice to get sane device name from vid/pid or some other info an OS/hal can give. That's easy to implement a simple hal addon that handle the filling of scanner.sane.name field. I wish you will understand that need. Kind regards, ?tienne. -- Verso l'Alto ! -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?= Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20061217/d5528193/attachment.pgp From bersac...@laposte.net Sun Dec 17 22:36:23 2006 From: bersac...@laposte.net (=?ISO-8859-1?Q?=C9tienne?= Bersac) Date: Tue Dec 19 19:42:50 2006 Subject: [sane-devel] SANE2 commitment In-Reply-To: 69ff73b20612171152h1110e1deleb7b80d30264...@mail.gmail.com References: 20061215175700.4c974c89@inspiron 45854deb.9010...@penguin-breeder.org 20061217172351.70067897@inspiron 45858d8f.6080...@zago.net 20061217201545.2a7c85c3@inspiron 4585998d.7030...@zago.net 20061217203458.10327e0e@inspiron 69ff73b20612171152h1110e1deleb7b80d30264...@mail.gmail.com Message-ID: 1166391382.5549.17.camel@thilivren Skipped content of type multipart/mixed-- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?= Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20061217/a9772311/attachment.pgp From bersac...@laposte.net Tue Dec 19 15:55:10 2006 From: bersac...@laposte.net (=?ISO-8859-1?Q?=C9tienne?= Bersac) Date: Tue Dec 19 20:19:59 2006 Subject: [sane-devel] SANE2 commitment In-Reply-To: 1166539654.30598.31.camel@casa References: 20061215175700.4c974c89@inspiron 45854deb.9010...@penguin-breeder.org 20061217172351.70067897@inspiron 45858d8f.6080...@zago.net 20061217201545.2a7c85c3@inspiron 4585998d.7030...@zago.net 20061217203458.10327e0e@inspiron 69ff73b20612171152h1110e1deleb7b80d30264...@mail.gmail.com 1166539654.30598.31.camel@casa Message-ID: 1166540109.5681.35.camel@thilivren Hi, That would be really nice. I wonder if this will only work on linux. What about *BSD, Solaris and Windows? I think that SANE must implement a modular OS - SANE API that allow OS to ask SANE to load a driver for one device and the monitor buttons, ? SANE should then also implement a legacy probe mecanism for other OSes or other purpose (distro not shiping HAL, etc.). ?tienne. -- Verso l'Alto ! -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?= Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20061219/36fc8090/attachment.pgp From bersac...@laposte.net Tue Dec 19 20:57:38 2006 From: bersac...@laposte.net (=?ISO-8859-1?Q?=C9tienne?= Bersac) Date: Tue Dec 19 22:58:39 2006 Subject: [sane-devel] Frontends : Gnome Scan 0.4 ! Message-ID: 1166558258.5681.99.camel@thilivren Hi all ! Gnome Scan 0.4 has been released with nice gui improvments and new features like x/y resolutions, computed area rotation, ? http://gnome-scan.blogspot.com/2006/12/releasing-04-is-your-app-people-ready.html ?tienne. -- Verso l'Alto ! -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Ceci est une partie de message =?ISO-8859
[sane-devel] SANE2 commitment
On Sunday 17 December 2006 22:47, Martin Owens wrote: Thanks for the link, See it sounds like you want to make the same mistakes, instead of looking for a better way to organise scanning in linux your looking at how to better organise functionality in sane. Just for the records: SANE is not intended to be Linux only! The problem is that the way scanning is organised is crack-pot and out dated. we are duplicating effort for no good reason other than to be stuck in our rut. He, he... I see so many opportunities to make sane a slim line routing code instead of a bloated detection and scanning library. Okay, go ahead, make some proposals -but keep in mind, that we will not only focus on Linux. - Gerhard [SNIPSNAP]
Fwd: Re: [sane-devel] SANE2 commitment
Guess this should go to the list too... -- Forwarded Message -- Subject: Re: [sane-devel] SANE2 commitment Date: Monday 18 December 2006 08:50 From: Martin Owens docto...@gmail.com To: Gerhard Jaeger gerh...@gjaeger.de I'm fine about it not being linux only, I just think we're limiting our options to be all things to all platforms. For instance, the back ends them selves do not need to be platform specific. but i believe sane integration 'how the backends are used' should be. Because at the end of the day all you really need to do is have a small amount of plugin code for linux hal, same for windows hal, other archs will need more thicker backend but that doesn't mean you need to force it on operating systems that already manage devices without blathering. If it turns out to be non-trivial then perhaps there ort to be a linux sane, call it less-sane 'linux embeded scanner support - sane' and we can all have a chuckle and use the same backend driver code. I just can't believe that we're stuck in the stone age of scanner device management because of bsd, I suspect that this is exactly the same reason gutten print is having device problems too, but at least they have better device code. On 12/18/06, Gerhard Jaeger gerh...@gjaeger.de wrote: On Sunday 17 December 2006 22:47, Martin Owens wrote: Thanks for the link, See it sounds like you want to make the same mistakes, instead of looking for a better way to organise scanning in linux your looking at how to better organise functionality in sane. Just for the records: SANE is not intended to be Linux only! The problem is that the way scanning is organised is crack-pot and out dated. we are duplicating effort for no good reason other than to be stuck in our rut. He, he... I see so many opportunities to make sane a slim line routing code instead of a bloated detection and scanning library. Okay, go ahead, make some proposals -but keep in mind, that we will not only focus on Linux. - Gerhard [SNIPSNAP]
[sane-devel] SANE2 commitment
I'm fine about it not being linux only, I just think we're limiting our options to be all things to all platforms. For instance, the back ends them selves do not need to be platform specific. but i believe sane integration 'how the backends are used' should be. Because at the end of the day all you really need to do is have a small amount of plugin code for linux hal, same for windows hal, other archs will need more thicker backend but that doesn't mean you need to force it on operating systems that already manage devices without blathering. If it turns out to be non-trivial then perhaps there ort to be a linux sane, call it less-sane 'linux embeded scanner support - sane' and we can all have a chuckle and use the same backend driver code. I just can't believe that we're stuck in the stone age of scanner device management because of bsd, I suspect that this is exactly the same reason gutten print is having device problems too, but at least they have better device code. On 12/18/06, Gerhard Jaeger gerh...@gjaeger.de wrote: On Sunday 17 December 2006 22:47, Martin Owens wrote: Thanks for the link, See it sounds like you want to make the same mistakes, instead of looking for a better way to organise scanning in linux your looking at how to better organise functionality in sane. Just for the records: SANE is not intended to be Linux only! The problem is that the way scanning is organised is crack-pot and out dated. we are duplicating effort for no good reason other than to be stuck in our rut. He, he... I see so many opportunities to make sane a slim line routing code instead of a bloated detection and scanning library. Okay, go ahead, make some proposals -but keep in mind, that we will not only focus on Linux. - Gerhard [SNIPSNAP] -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] SANE2 commitment
On Mon, 18 Dec 2006, Martin Owens wrote: I'm fine about it not being linux only, I just think we're limiting our options to be all things to all platforms. For instance, the back ends them selves do not need to be platform specific. but i believe sane integration 'how the backends are used' should be. agreed- especially because there are lots of users of linux distros that still dont use HAL :) allan Because at the end of the day all you really need to do is have a small amount of plugin code for linux hal, same for windows hal, other archs will need more thicker backend but that doesn't mean you need to force it on operating systems that already manage devices without blathering. If it turns out to be non-trivial then perhaps there ort to be a linux sane, call it less-sane 'linux embeded scanner support - sane' and we can all have a chuckle and use the same backend driver code. I just can't believe that we're stuck in the stone age of scanner device management because of bsd, I suspect that this is exactly the same reason gutten print is having device problems too, but at least they have better device code. On 12/18/06, Gerhard Jaeger gerh...@gjaeger.de wrote: On Sunday 17 December 2006 22:47, Martin Owens wrote: Thanks for the link, See it sounds like you want to make the same mistakes, instead of looking for a better way to organise scanning in linux your looking at how to better organise functionality in sane. Just for the records: SANE is not intended to be Linux only! The problem is that the way scanning is organised is crack-pot and out dated. we are duplicating effort for no good reason other than to be stuck in our rut. He, he... I see so many opportunities to make sane a slim line routing code instead of a bloated detection and scanning library. Okay, go ahead, make some proposals -but keep in mind, that we will not only focus on Linux. - Gerhard [SNIPSNAP] -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org -- so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls - Max Cavalera
[sane-devel] SANE2 commitment
On Friday 15 December 2006 17:57, Alessandro Zummo wrote: Hello developers, since there seems to be interest in developing sane2, I've decided to start this thread in order to collect the commitment of each developer. I'm willing to port the epson driver to sane2, help porting the coolscan driver and handle the command line frontend. I think Giuseppe Sacco has showed interest to do coolscan bits. A friend of mine, Stefano Merlo, has committed himself to the canon driver. I'd appreciate if everyone who is interested can reply with their own commitments for the 2007.. ehm.. sane2 :) I'll do the plustek stuff (maybe also plustek_pp and u12) If needed I'll also check the sanei_thread stuff. Regarding the plustek_pp: I don't think we should support parport devices any longer. One thing: I'd like to see Hennings opinion here! And we should agree on some version of the SANE2 standard... Ciao Gerhard
[sane-devel] SANE2 commitment
On Sun, 17 Dec 2006 12:49:04 +0100 (MET) Gerhard Jaeger gerh...@gjaeger.de wrote: I'd appreciate if everyone who is interested can reply with their own commitments for the 2007.. ehm.. sane2 :) I'll do the plustek stuff (maybe also plustek_pp and u12) If needed I'll also check the sanei_thread stuff. great, thanks! Regarding the plustek_pp: I don't think we should support parport devices any longer. they are, in fact, kludgy. we might start without them. there's always the chance to add them if the need arises. One thing: I'd like to see Hennings opinion here! And we should me too! agree on some version of the SANE2 standard... when the dev team will be in place we might run a bunch of quick polls in order to make some fundamental choices (c99, data types, ...). -- Best regards, Alessandro Zummo, Tower Technologies - Turin, Italy http://www.towertech.it
[sane-devel] SANE2 commitment
On Sunday 17 December 2006 15:02, Jochen Eisinger wrote: Hi, Alessandro Zummo wrote: I'd appreciate if everyone who is interested can reply with their own commitments for the 2007.. ehm.. sane2 :) I'm quite surprised to hear there is a sane2 standard - at least one that we can easily start to implement. I don't think it's a good idea to start hacking something before it's clear we have a standard that will support us for the next few years. Hi, in general I'd say: yes you are right. But on the other hand I don't see any real progress since years regarding SANE2 - so the question is: Stay/stuck on SANE1 w/o any chance to enhance support for recent devices OR start with a standard that has not been finished yet... What needs to be done to finish the standard? Is anybody able to point out the open issues? -Gerhard
[sane-devel] SANE2 commitment
On Sun, 17 Dec 2006 15:02:19 +0100 Jochen Eisinger joc...@penguin-breeder.org wrote: Hi, Alessandro Zummo wrote: I'd appreciate if everyone who is interested can reply with their own commitments for the 2007.. ehm.. sane2 :) I'm quite surprised to hear there is a sane2 standard - at least one that we can easily start to implement. I don't think it's a good idea to start hacking something before it's clear we have a standard that will support us for the next few years. you're right. my idea is to rally up some developers and then define the standard. only then we should start hacking. however, defining the standard without the developers will not lead us to anything useful. some people has committed the time necessary to port to sane2 the first bunch of drivers. we are currently missing coders for - all of sanei/* (i'll take sanei_tcp) - the build system (configure, makefile et al) - X11 frontends -- Best regards, Alessandro Zummo, Tower Technologies - Turin, Italy http://www.towertech.it
[sane-devel] SANE2 commitment
Alessandro Zummo wrote: On Sun, 17 Dec 2006 15:02:19 +0100 Jochen Eisinger joc...@penguin-breeder.org wrote: Hi, Alessandro Zummo wrote: I'd appreciate if everyone who is interested can reply with their own commitments for the 2007.. ehm.. sane2 :) I'm quite surprised to hear there is a sane2 standard - at least one that we can easily start to implement. I don't think it's a good idea to start hacking something before it's clear we have a standard that will support us for the next few years. you're right. my idea is to rally up some developers and then define the standard. only then we should start hacking. however, defining the standard without the developers will not lead us to anything useful. some people has committed the time necessary to port to sane2 the first bunch of drivers. we are currently missing coders for - all of sanei/* (i'll take sanei_tcp) - the build system (configure, makefile et al) - X11 frontends I believe the right approach is to fork the existing tree and start fixing and adding functionalities to it. That way you'll keep something that works all the time, saving many headaches. As or for the sane2 standard, it's only just a piece of paper right now. Coding should determine what will stay and what will go away, not the opposite (cathedral vs bazaar). Frank.
[sane-devel] SANE2 commitment
Alessandro Zummo wrote: Hello developers, since there seems to be interest in developing sane2, I've decided to start this thread in order to collect the commitment of each developer. I'm willing to port the epson driver to sane2, help porting the coolscan driver and handle the command line frontend. I think Giuseppe Sacco has showed interest to do coolscan bits. A friend of mine, Stefano Merlo, has committed himself to the canon driver. I'd appreciate if everyone who is interested can reply with their own commitments for the 2007.. ehm.. sane2 :) I can port mine. Frank.
[sane-devel] SANE2 commitment
On Sun, 17 Dec 2006 19:33:51 +0100 Frank Zago fr...@zago.net wrote: some people has committed the time necessary to port to sane2 the first bunch of drivers. we are currently missing coders for - all of sanei/* (i'll take sanei_tcp) - the build system (configure, makefile et al) - X11 frontends I believe the right approach is to fork the existing tree and start fixing and adding functionalities to it. That way you'll keep something that works all the time, saving many headaches. As or for the sane2 standard, it's only just a piece of paper right now. Coding should determine what will stay and what will go away, not the opposite (cathedral vs bazaar). so you're saying to declare current sane as stable, fork it and add features to the new tree, making it morphing into something that will be the next sane? -- Best regards, Alessandro Zummo, Tower Technologies - Turin, Italy http://www.towertech.it
[sane-devel] SANE2 commitment
Alessandro Zummo wrote: On Sun, 17 Dec 2006 19:33:51 +0100 Frank Zago fr...@zago.net wrote: some people has committed the time necessary to port to sane2 the first bunch of drivers. we are currently missing coders for - all of sanei/* (i'll take sanei_tcp) - the build system (configure, makefile et al) - X11 frontends I believe the right approach is to fork the existing tree and start fixing and adding functionalities to it. That way you'll keep something that works all the time, saving many headaches. As or for the sane2 standard, it's only just a piece of paper right now. Coding should determine what will stay and what will go away, not the opposite (cathedral vs bazaar). so you're saying to declare current sane as stable, fork it and add features to the new tree, making it morphing into something that will be the next sane? Yes. I think sane1 can evolve into sane2 step by step so as to keep a working tree.
[sane-devel] SANE2 commitment
On Sun, 17 Dec 2006 20:25:01 +0100 Frank Zago s...@zago.net wrote: so you're saying to declare current sane as stable, fork it and add features to the new tree, making it morphing into something that will be the next sane? Yes. I think sane1 can evolve into sane2 step by step so as to keep a working tree. well, I'm open to this possibility. I just need to add a new sane frame format after all :) -- Best regards, Alessandro Zummo, Tower Technologies - Turin, Italy http://www.towertech.it
[sane-devel] SANE2 commitment
On Sun, 2006-12-17 at 19:37 +0100, Frank Zago wrote: Alessandro Zummo wrote: On Sun, 17 Dec 2006 15:02:19 +0100 Jochen Eisinger joc...@penguin-breeder.org wrote: Hi, Alessandro Zummo wrote: I'd appreciate if everyone who is interested can reply with their own commitments for the 2007.. ehm.. sane2 :) I'm quite surprised to hear there is a sane2 standard - at least one that we can easily start to implement. I don't think it's a good idea to start hacking something before it's clear we have a standard that will support us for the next few years. you're right. my idea is to rally up some developers and then define the standard. only then we should start hacking. however, defining the standard without the developers will not lead us to anything useful. some people has committed the time necessary to port to sane2 the first bunch of drivers. we are currently missing coders for - all of sanei/* (i'll take sanei_tcp) - the build system (configure, makefile et al) - X11 frontends I believe the right approach is to fork the existing tree and start fixing and adding functionalities to it. That way you'll keep something that works all the time, saving many headaches. As or for the sane2 standard, it's only just a piece of paper right now. Coding should determine what will stay and what will go away, not the opposite (cathedral vs bazaar). Frank. One other step is to check which bugreports can be solved before such a fork. -- m.vr.gr. Gerard Klaver
[sane-devel] SANE2 commitment
My point of view is that it is better to identify the problems you wish to solve my creating a new version of sane that the current version of sane can not be developed into. The first problem I've noted with sane is that it is a little bit all mixed up, detection mixed with scaning, paraport mixed with usb. not good. If you are going to start a new direction and really give it some weight behind it I suggest the following: For device detection and management use HAL, update hal dbus code with all existing detection and status code which will keep these devices happy, enable the modification of the hal xml as a simple way of keeping track of which scanners work with which backends too, removing this from the backend code is a must. You can then change your clients to use hal and simply call dbus commands to scan etc. Paraport scanners need continued support, we don't just drop support because something better has come a long. we should try to work with the hal team and how their dealing with passive devices on para and serial ports, we might be able to come up with something good that allows the best combination of user selection and computer detection. For the drivers them sevles, obviously use of libusb is good, but the idea that libsane is a background package which doesn't offer anything it's self is quite desirable. giving distributers the option of installing some or all scanner backends. as long as device detection etc is handled by hal then it won't even be a problem to have sane request the right backend be installed upon use. You can tell I've given this a lot of thought, sane was going to be my next project to work on because I was sick to death of setting up scanners with it. On 12/17/06, Alessandro Zummo azummo-li...@towertech.it wrote: On Sun, 17 Dec 2006 20:25:01 +0100 Frank Zago s...@zago.net wrote: so you're saying to declare current sane as stable, fork it and add features to the new tree, making it morphing into something that will be the next sane? Yes. I think sane1 can evolve into sane2 step by step so as to keep a working tree. well, I'm open to this possibility. I just need to add a new sane frame format after all :) -- Best regards, Alessandro Zummo, Tower Technologies - Turin, Italy http://www.towertech.it -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] SANE2 commitment
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alessandro Zummo wrote: Hello developers, since there seems to be interest in developing sane2, I've decided to start this thread in order to collect the commitment of each developer. I'm willing to port the epson driver to sane2, help porting the coolscan driver and handle the command line frontend. I think Giuseppe Sacco has showed interest to do coolscan bits. A friend of mine, Stefano Merlo, has committed himself to the canon driver. I'd appreciate if everyone who is interested can reply with their own commitments for the 2007.. ehm.. sane2 :) Just for everyone's info, the latest proposal for sane 2 (as far as I know) can be found here: http://www.sane-project.org/sane2/ (Dec. 8, 2002, has it been that long... :) ) Kind regards, Bertrik -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFhbSHETD6mlrWxPURAtDoAKC4A7tMaNMVZH8WFEeuJREfwP2hIgCgjuoL LzZ7FoobSmohsMGPFDIKt0M= =Yv0P -END PGP SIGNATURE-
[sane-devel] SANE2 commitment
Thanks for the link, See it sounds like you want to make the same mistakes, instead of looking for a better way to organise scanning in linux your looking at how to better organise functionality in sane. The problem is that the way scanning is organised is crack-pot and out dated. we are duplicating effort for no good reason other than to be stuck in our rut. I see so many opportunities to make sane a slim line routing code instead of a bloated detection and scanning library. On 12/17/06, Bertrik Sikken bert...@sikken.nl wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alessandro Zummo wrote: Hello developers, since there seems to be interest in developing sane2, I've decided to start this thread in order to collect the commitment of each developer. I'm willing to port the epson driver to sane2, help porting the coolscan driver and handle the command line frontend. I think Giuseppe Sacco has showed interest to do coolscan bits. A friend of mine, Stefano Merlo, has committed himself to the canon driver. I'd appreciate if everyone who is interested can reply with their own commitments for the 2007.. ehm.. sane2 :) Just for everyone's info, the latest proposal for sane 2 (as far as I know) can be found here: http://www.sane-project.org/sane2/ (Dec. 8, 2002, has it been that long... :) ) Kind regards, Bertrik -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFhbSHETD6mlrWxPURAtDoAKC4A7tMaNMVZH8WFEeuJREfwP2hIgCgjuoL LzZ7FoobSmohsMGPFDIKt0M= =Yv0P -END PGP SIGNATURE- -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] SANE2 commitment
Hi, On 2006-12-17 16:43, Gerhard Jaeger wrote: in general I'd say: yes you are right. But on the other hand I don't see any real progress since years regarding SANE2 - so the question is: Stay/stuck on SANE1 w/o any chance to enhance support for recent devices OR start with a standard that has not been finished yet... There is no need to do it only one way. You could write a meta backend (like dll) that connects to a sane2 frontend and translates sane2 api to sane1 and loads sane1 backends. So you'd only update the maintained or new backends to sane2 and let the meta backend do the reast for the old ones. What needs to be done to finish the standard? Is anybody able to point out the open issues? http://www.sane-project.org/sane2/sane2-todo.html And more generally: http://www.sane-project.org/sane2/sane2-todo.html There is already a branch in CVS for SANE2 (see above), it has only the docs, no code yet. Bye, Henning
[sane-devel] SANE2 commitment
Hi, On 2006-12-17 12:49, Gerhard Jaeger wrote: One thing: I'd like to see Hennings opinion here! And we should agree on some version of the SANE2 standard... Unfortunately I'm very busy and can't do any work related to SANE2 in the near future. I'd really appreciate a new effort in this direction. However, please everybody read all the old threads about SANE2. There was already a lot of discussion and the details are NOT easy. So before everybody starts programming, at least the basic ideas of SANE2 should be fixed. Some points like the image formats and the error handling really need to be finally decided. Bye, Henning
[sane-devel] SANE2 commitment
Hi, Alessandro Zummo wrote: I'd appreciate if everyone who is interested can reply with their own commitments for the 2007.. ehm.. sane2 :) I'm quite surprised to hear there is a sane2 standard - at least one that we can easily start to implement. I don't think it's a good idea to start hacking something before it's clear we have a standard that will support us for the next few years. regards -- jochen
[sane-devel] SANE2 commitment
Hi everybody, On 2006-12-15 17:57, Alessandro Zummo wrote: since there seems to be interest in developing sane2, I've decided to start this thread in order to collect the commitment of each developer. [...] Could we please move the SANE2 (and any sane-standard related) topics to the sane-standard mailing list? That's the idea of that list ... SANE2 threads tend to create lot of traffic that is less interesting for users and even some programmers. So lets focus it in sane-standard. sane-standard is moderated to avoid off-topic. Frequent posters will be automatically moderated. Others may take one day time to be approved. More moderators for this and the other SANE mailing lists are wanted. Volunteers please contact me. Bye, Henning
[sane-devel] SANE2 commitment
Hello developers, since there seems to be interest in developing sane2, I've decided to start this thread in order to collect the commitment of each developer. I'm willing to port the epson driver to sane2, help porting the coolscan driver and handle the command line frontend. I think Giuseppe Sacco has showed interest to do coolscan bits. A friend of mine, Stefano Merlo, has committed himself to the canon driver. I'd appreciate if everyone who is interested can reply with their own commitments for the 2007.. ehm.. sane2 :) -- Best regards, Alessandro Zummo, Tower Technologies - Turin, Italy http://www.towertech.it
[sane-devel] SANE2 commitment
I can do dell1600n_net. Anyone volunteering some kind of SANE2 frontend to test with?! cheers, Jon == Jon Chambers = http://www.jon.demon.co.uk, 020 8575 7097, 07931 961669 = On Fri, 15 Dec 2006, Alessandro Zummo wrote: since there seems to be interest in developing sane2, I've decided to start this thread in order to collect the commitment of each developer. I'm willing to port the epson driver to sane2, help porting the coolscan driver and handle the command line frontend. []
[sane-devel] SANE2 commitment
On Fri, 15 Dec 2006, Alessandro Zummo wrote: Hello developers, since there seems to be interest in developing sane2, I've decided to start this thread in order to collect the commitment of each developer. I'm willing to port the epson driver to sane2, help porting the coolscan driver and handle the command line frontend. I think Giuseppe Sacco has showed interest to do coolscan bits. A friend of mine, Stefano Merlo, has committed himself to the canon driver. I'd appreciate if everyone who is interested can reply with their own commitments for the 2007.. ehm.. sane2 :) m. allan noah will port fujitsu allan -- so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls - Max Cavalera
[sane-devel] SANE2 commitment
On Fri, 2006-12-15 at 17:57 +0100, Alessandro Zummo wrote: Hello developers, since there seems to be interest in developing sane2, I've decided to start this thread in order to collect the commitment of each developer. I'm willing to port the epson driver to sane2, help porting the coolscan driver and handle the command line frontend. I think Giuseppe Sacco has showed interest to do coolscan bits. A friend of mine, Stefano Merlo, has committed himself to the canon driver. I'd appreciate if everyone who is interested can reply with their own commitments for the 2007.. ehm.. sane2 :) -- Best regards, Alessandro Zummo, Tower Technologies - Turin, Italy http://www.towertech.it For me the stv680 backend -- m.vr.gr. Gerard Klaver
