From kde-devel Wed Oct 21 16:38:08 2009 From: Eduard Huguet Date: Wed, 21 Oct 2009 16:38:08 +0000 To: kde-devel Subject: Re: Re: Kooka KDE4 now in SVN Message-Id: <617be8890910210938i46a62a04r784bc49a37a839e3 () mail ! gmail ! com> X-MARC-Message: https://marc.info/?l=kde-devel&m=125614317432415 > Message: 3 > Date: Tue, 20 Oct 2009 14:38:33 +0200 > From: Giovanni Venturi > Subject: Re: Kooka KDE4 now in SVN > To: kde-devel@kde.org > Message-ID: >        <6073258b0910200538i351fb0b1w43c94e0ae88ad6e5@mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > If I've got some spare time I could try to give help for porting. I'm the > Italian translator of Kooka when it was in KDE 3 :) . I used so much time > that application. > Sorry if I ask (I didn't followed all the thread) can you summerize in few > words why don't help skanlite instead of backing back to life Kooka :) ? > > Giovanni Well, I wouldn't like to start a discussion here, but the question is also valid in the opposite way: I mean, ¿why create a new project (Skanlite) instead of porting an old, excellent and reliable one like Kooka? Anyway, I made the proposal mainly because I'm very used to Kooka (still currently using it under KDE4), and I didn't understand (and still don't) the reasons for creating a brand new program for scanning instead of porting the old one. And I though also it would be a good way for me to introduce myself into KDE programming, which I'm interested in, specifically in an area in which I have some technical background. After the initial proposal a number of ideas and questions have arised, like unifying all scanning code into a single one library (thus deprecating libkscan in favour of libksane), developing a kipi plugin, etc... All them seem good ideas for me, but anyway an initial KDE4 porting job of the existing Kooka code is in any case a good idea. Once done, we can look for the better way to integrate the different routines into a single library. Regards, Eduard >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<