Collaboration between KDE printing development team and Linspire

[Jeremy Shaw]

Hello,

I have not had time to review everything, but in the meantime, I have
attached a patch that might be interesting.

At some point in time, samba printer scanning stopped working for
us. The kde printing scanning code works by calling nmblookup and
parsing the output (or, at least, that is how it works in 3.3.2, not
sure if it has been updated).

I modified our version to use libsmbclient instead, and it seems to be
more reliable. 

The patch was lifted from the code I wrote for sharemanager,
(http://www.linspire.com/lindows_products_details.php?product_id=9444&pg=specs),
so there are a few things that need to be done before it can be folded
into KDE:

(1) remove the extra cruft not needed by kdeprint 

(2) reformat to match coding standard 

(3) Look at the comments (especially ones starting with JAS), and
    decide if any of the issues described in the comments need to be
    addressed.

(4) Add kwallet support(?) -- this should be pretty easy. I have
    already added it to sharemanager.

Let me know if this patch is of interest to you guys, and we can go
from there.

Jeremy Shaw.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: samba-scanning.patch
Type: application/octet-stream
Size: 12468 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-print/attachments/20050912/025942f0/samba-scanning.obj
-------------- next part --------------


At Mon, 22 Aug 2005 13:18:28 -0700,
Jeremy Shaw wrote:
> 
> Hello,
> 
> An easy start would be for me to put together a list of changes we
> have already made or plan on making. I can provide diffs for the
> patches we have already made.
> 
> I will need to work with my manager to figure out a reasonable
> schedule for this.
> 
> Jeremy Shaw.
> 
> At Mon, 22 Aug 2005 11:33:36 -0700,
> Tom Welch wrote:
> > 
> > [1  <text/plain; ISO-8859-2 (7bit)>]
> > Cristian, I don't think that we have any usability studies on the 
> > printing system per say.  However we have in the past and do regularlly 
> > make improvements for our users.  I'm including Jeremy Shaw who is our 
> > engineer in charge of this area and he can work closely with you.  Keep 
> > me on the CC line so that I can monitor things as well.
> > 
> > Thanks and let's make some good things happen!
> > 
> > Tom
> > 
> > Cristian Tibirna wrote:
> > 
> > >On 19 August 2005 18:35, Tom Welch wrote:
> > >  
> > >
> > >>Christian,
> > >>
> > >>I'm happy to work with you and your team.  How do you propose we work
> > >>together?
> > >>    
> > >>
> > >
> > >Hello Tom
> > >
> > >Nice to hear from you.
> > >
> > >Well, my discussion with Kevin and Randy turned around the fact that usability 
> > >and user experience of the KDE printing tools could be improved. I concluded 
> > >that Linspire might have a database of user reports, or migh have done (or 
> > >have intention to do) scientific usability studies.
> > >
> > >Thus, the KDE community would be very pleased to collaborate with Linspire in 
> > >this kind of work. I must say that I didn't have occasions to use Linspire, 
> > >but I gather that a large part of KDE is directly used as is in your 
> > >products. So, all improvements in KDE are automatically reflected in 
> > >Linspire. Thus, I believe that it would be very beneficial to all of us, 
> > >those involved in this discussion, if Linspire would provide results of 
> > >usability studies or, even better, the code modifications resulted from such.
> > >
> > >This is a first step. There are many other possibilities of cooperation, and I 
> > >think we would come to them in time.
> > >
> > >Thanks a lot for your attention.
> > >
> > >  
> > >
> > 
> > -- 
> > 
> > * <http://www.linspire.com>
> >   Tom Welch*
> > Chief Technical Officer
> > Linspire, Inc.
> > Work: 858-587-6700 Ext. 254
> > Cell: 858-829-4614
> > www.linspire.com <http://www.linspire.com>
> > tom at linspire.com <mailto:tom at linspire.com>
> > 
> > 	  	
> > 
> > /*1 CNR a day*/
> > <http://www.linspire.com/cnr>
> > /*That's all we ask*/
> > 
> > 
> > [2  <multipart/related (7bit)>]