[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Kooka KDE4 now in SVN
From:       Kåre_Särs <kare.sars () iki ! fi>
Date:       2009-10-22 8:47:21
Message-ID: 200910221147.22075.kare.sars () iki ! fi
[Download RAW message or body]

On Wednesday 21 October 2009, Eduard Huguet wrote:
> > Date: Tue, 20 Oct 2009 14:38:33 +0200
> > From: Giovanni Venturi <giovanni@ksniffer.org>

> > 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?

That is a valid question and the simple/short answer is that my main aim was 
not the application but the scanning library. 

Here is a link to previous discussion/motivation:
http://lists.kde.org/?l=kde-core-devel&m=120690579429463&w=2 

If you check out the application code for Skanlite you see that the 
application is only a small "save this acquired image" type of application 
(<800 lines of code).

> 
> 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.

So if somebody wants to use libksane in a KookaNG I'm more than happy, and I 
am open to discussion about the API.
 
> 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.

Plugins:
 -ksaneplugin, in kdegraphics, is a drop-in replacement for the libkscan.

 -The KDE4 acquireimage kipi-plugin was the first code to use libksane (even 
before Skanlite)


To conclude, I think it is good that there is interest in making an advanced 
scanning application. (And I hope it will use libksane for the scanning ;)

Regards,
   Kåre

P.s. There was once an idea of making a collection of applications (like 
Kontact), with each application specialized in different scanning tasks.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]