[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: Volunteering to port Kooka to KDE4
From: Eduard Huguet <eduardhc () gmail ! com>
Date: 2009-10-17 13:50:21
Message-ID: 617be8890910170650u12701d2fmf03c093bd72ce5a7 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
>
> Message: 8
> Date: Fri, 16 Oct 2009 22:03:55 +0100
> From: Jonathan Marten <jjm2@keelhaul.demon.co.uk>
> Subject: Re: Volunteering to port Kooka to KDE4
> To: kde-devel@kde.org
> Message-ID: <ovws2vt5j8.fsf@keelhaul.local>
> Content-Type: text/plain; charset=iso-8859-1
>
> Good to hear from you Eduard. A timely message, showing that porting
> offers are like buses - you wait for ages and then several come along
> at once...
>
> I must admit that I'd let development on the KDE3 version stall for a
> while, for no other reason than it had got to a fairly stable and
> usable state. Two areas that I'd been intending to address are the
> dock window user interface (particularly unreliable) and a move to
> Skanlite's scanning library (libksane). There was no point in trying
> to do these in the KDE3 version, though, so the KDE4 port would have
> to come first.
>
> Currently I'm in the process of porting libkscan and Kooka to KDE4,
> with the intention of doing a straightforward conversion before
> attempting any major internal changes - if there are to be any, these
> will be easier to do when the basic application is working. Just this
> morning I finished the last class conversion and got an executable,
> which promptly crashed... so there is some work to do.
>
> I'd been intending to create a new SVN work branch as soon as the
> basic application was working, but if others are interested in the
> code then I can do that now so that anyone else interested can at
> least use it as a base.
>
> Other major porting areas are the migration of K3 and Q3 classes,
> printing and DBUS (there wasn't any DCOP in the original, but remote
> control of a scanner would be most useful). Assistance with these
> from anyone would be most welcome!
>
> > I'm aware of the existence of the Skanlite project, but however I
> > consider that Kooka is, right now, a fairly superior scanning
> > application for KDE that it's really worth the effort of migrating
> > it.
>
> But even if we want to keep the Kooka GUI, it would be of benefit
> (i.e. a single scanning library, 16-bit scanner support) to convert
> Kooka to use libksane. Currently the libkscan library is a mess of
> GUI, scanner interfacing and image handling all together.
>
> > How should I proceed? I have some background in general Qt3 and Qt4
> > developing (including porting issues), and general experience
> > working with KDE API. I'm well aware of the difficulty of the
> > process, but nevertheless I'd like to at least try to do it (can't
> > promise any results, though...) Best regards, ? Eduard Huguet
>
> If you could hang on for a while, I'll get a KDE4 development branch
> set up and push what I have at the moment to it - no guarantees that
> anything will work though! Things that you could work on at the
> moment in your source base, while awaiting that, are printing or
> porting of uses of Q3ButtonGroup/Q3GroupBox/Q3ScrollView - these are
> the main areas where I've just used the compatibility classes or
> commented out for now.
>
> > PS: I've started by taking the original source code from Kooka site
> > and converting it to use CMake build system instead of
> > Autotools. Currently I've just started migrating classes, but I just
> > prefer to announce it here just in case anyone is also trying to do
> > it, or else this could cause any kind of imaginable? trouble...
>
> Many thanks for your message and your offer, apologies again for
> allowing things to stay dormant for so long. If you are interested,
> there is certainly work to be done!
>
> Regards, Jonathan
> (Current Kooka maintainer)
>
> --
> Jonathan Marten http://www.keelhaul.demon.co.uk
> Twickenham, UK jjm2@keelhaul.demon.co.uk
>
>
Wow, that obviously changes things (for good!). I just had started to
migrate classes, but if you have finished this part then it doesn't make
sense for me to do the same thing.
I just had created a new project in Assembla for the migration process (
http://www.assembla.com/spaces/kooka4), but it would really make sense if
you could create, as you say, a development branch in any place so we could
start working together. At this stage, it really doesn't care if the code
currently compiles or anything, it's just to have a common start point to
continuate from.
I'm willing to collaborate with you in this, I find this project a rather
motivating one for me to introduce myself into KDE developing. As I said in
the initial mail, I can't promise anything, but I think I can dedicate at
least 2 or 3 hours a week for this, so maybe we can get to something
finally.
I'll leave the things "as is" until I get any response from you.
Thanks in advance,
Eduard Huguet
PS: to the others, thank you all for the feedback and the ideas. I really
hope we can give course to some of the presented ideas, as they are really
interesting.
[Attachment #5 (text/html)]
<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: \
1ex;">
Message: 8<br>
Date: Fri, 16 Oct 2009 22:03:55 +0100<br>
From: Jonathan Marten <<a \
href="mailto:jjm2@keelhaul.demon.co.uk">jjm2@keelhaul.demon.co.uk</a>><br>
Subject: Re: Volunteering to port Kooka to KDE4<br>
To: <a href="mailto:kde-devel@kde.org">kde-devel@kde.org</a><br>
Message-ID: <ovws2vt5j8.fsf@keelhaul.local><br>
Content-Type: text/plain; charset=iso-8859-1<br>
<br>
Good to hear from you Eduard. A timely message, showing that porting<br>
offers are like buses - you wait for ages and then several come along<br>
at once...<br>
<br>
I must admit that I'd let development on the KDE3 version stall for a<br>
while, for no other reason than it had got to a fairly stable and<br>
usable state. Two areas that I'd been intending to address are the<br>
dock window user interface (particularly unreliable) and a move to<br>
Skanlite's scanning library (libksane). There was no point in trying<br>
to do these in the KDE3 version, though, so the KDE4 port would have<br>
to come first.<br>
<br>
Currently I'm in the process of porting libkscan and Kooka to KDE4,<br>
with the intention of doing a straightforward conversion before<br>
attempting any major internal changes - if there are to be any, these<br>
will be easier to do when the basic application is working. Just this<br>
morning I finished the last class conversion and got an executable,<br>
which promptly crashed... so there is some work to do.<br>
<br>
I'd been intending to create a new SVN work branch as soon as the<br>
basic application was working, but if others are interested in the<br>
code then I can do that now so that anyone else interested can at<br>
least use it as a base.<br>
<br>
Other major porting areas are the migration of K3 and Q3 classes,<br>
printing and DBUS (there wasn't any DCOP in the original, but remote<br>
control of a scanner would be most useful). Assistance with these<br>
from anyone would be most welcome!<br>
<br>
> I'm aware of the existence of the Skanlite project, but however I<br>
> consider that Kooka is, right now, a fairly superior scanning<br>
> application for KDE that it's really worth the effort of migrating<br>
> it.<br>
<br>
But even if we want to keep the Kooka GUI, it would be of benefit<br>
(i.e. a single scanning library, 16-bit scanner support) to convert<br>
Kooka to use libksane. Currently the libkscan library is a mess of<br>
GUI, scanner interfacing and image handling all together.<br>
<br>
> How should I proceed? I have some background in general Qt3 and Qt4<br>
> developing (including porting issues), and general experience<br>
> working with KDE API. I'm well aware of the difficulty of the<br>
> process, but nevertheless I'd like to at least try to do it (can't<br>
> promise any results, though...) Best regards, ? Eduard Huguet<br>
<br>
If you could hang on for a while, I'll get a KDE4 development branch<br>
set up and push what I have at the moment to it - no guarantees that<br>
anything will work though! Things that you could work on at the<br>
moment in your source base, while awaiting that, are printing or<br>
porting of uses of Q3ButtonGroup/Q3GroupBox/Q3ScrollView - these are<br>
the main areas where I've just used the compatibility classes or<br>
commented out for now.<br>
<br>
> PS: I've started by taking the original source code from Kooka site<br>
> and converting it to use CMake build system instead of<br>
> Autotools. Currently I've just started migrating classes, but I just<br>
> prefer to announce it here just in case anyone is also trying to do<br>
> it, or else this could cause any kind of imaginable? trouble...<br>
<br>
Many thanks for your message and your offer, apologies again for<br>
allowing things to stay dormant for so long. If you are interested,<br>
there is certainly work to be done!<br>
<br>
Regards, Jonathan<br>
(Current Kooka maintainer)<br>
<br>
--<br>
Jonathan Marten <a href="http://www.keelhaul.demon.co.uk" \
target="_blank">http://www.keelhaul.demon.co.uk</a><br> Twickenham, UK \
<a href="mailto:jjm2@keelhaul.demon.co.uk">jjm2@keelhaul.demon.co.uk</a><br> \
<br></blockquote><div><br>Wow, that obviously changes things (for good!). I just had \
started to migrate classes, but if you have finished this part then it doesn't \
make sense for me to do the same thing.<br><br>I just had created a new project in \
Assembla for the migration process (<a \
href="http://www.assembla.com/spaces/kooka4">http://www.assembla.com/spaces/kooka4</a>), \
but it would really make sense if you could create, as you say, a development branch \
in any place so we could start working together. At this stage, it really doesn't \
care if the code currently compiles or anything, it's just to have a common start \
point to continuate from.<br> <br>I'm willing to collaborate with you in this, I \
find this project a rather motivating one for me to introduce myself into KDE \
developing. As I said in the initial mail, I can't promise anything, but I think \
I can dedicate at least 2 or 3 hours a week for this, so maybe we can get to \
something finally.<br> <br>I'll leave the things "as is" until I get \
any response from you.<br><br>Thanks in advance, <br> Eduard Huguet<br><br>PS: to \
the others, thank you all for the feedback and the ideas. I really hope we can give \
course to some of the presented ideas, as they are really interesting.<br> \
<br><br><br><br> <br></div></div><br>
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic