[Ktechlab-devel] Porting to Qt 4 --> I'd like to help

[Juan De Vincenzo]

Hi there,

Well, after a lot of reading I finally found the time to sit in front
of the machine and I was able to complete part of the porting. Overall
the process took around one hour and a half.

Attached you have a small log file I've created during the process to
document what I was doing. Hope it is clear enough, even though you
should keep in mind that it was done on the fly. I'll try to give it
some format when I have the time.

The thing is that now the remaining task (among others) is one with
which I require some assistance because it involves modifying the
code, which I'm still not ready to do. This is migrating the code from
DCOP to DBUS, and of course there will be some more things to fine
tune, but those can be handled at its time. Anyone could help with
that?

Also, please let me know if you think that there's anything missing or
that I didn't do properly. By the way, I have the ported code here on
my machine, would you like to take a look at it? How can I pass it
over to you? Maybe I can upload it somewhere?

By the way, this was my main guide for carrying this out:
http://techbase.kde.org/Development/Tutorials/KDE4_Porting_Guide

I'm really keen for your feedback. =)

Regards,
Juan

On Thu, Jan 29, 2009 at 1:49 AM, Juan De Vincenzo
<juandevincenzo at gmail.com> wrote:
> Thanks for your feedback.
>
> I've been taking a look at the porting tool and what I understand,
> based on what I've been reading[1], is that in order to do it all at
> once the whole project should count with a qt project file (*.pro).
> AFAIK Ktechlab doesn't use that, so I guess it is a file by file job
> that needs to be done.
>
> I'll keep researching the way to pull this off and send an update as
> soon as I have something. I guess the first thing I'll try is porting
> one or two files, maybe one small and another large (ktechlab.cpp) and
> learn how the process works.
>
> I'll also see if maybe a bash script can help automate the process for
> the whole source code. =)
>
> There's also the fact that .ui files also have to be ported to Qt4.
>
> Regards,
> Juan
>
> [1]http://doc.trolltech.com/4.0/qt3to4.html#qt3to4
>
> On Wed, Jan 28, 2009 at 6:06 PM, Chitlesh GOORAH <chitlesh at waeckerlin.de> wrote:
>> On Wed, Jan 28, 2009 at 9:45 AM, Juan De Vincenzo  wrote:
>>>
>>> For example a question that comes to my mind now is: would you use the
>>> qt3toqt4 porting tool or rather rewrite the code around Qt 4?
>>>
>>
>> Hello,
>> I would say, does it take a lot of time to port it with qt3qt4 ?
>> If it is about 4hrs of work, maybe you can give it a try and upload it
>> somewhere for testing.
>>
>> I have here for testing.
>>
>> Kind regards,
>> Chitlesh
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
>> _______________________________________________
>> Ktechlab-devel mailing list
>> Ktechlab-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/ktechlab-devel
>>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ktechlab_migration_short
Type: application/octet-stream
Size: 31026 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/ktechlab-devel/attachments/20090203/415e1da8/attachment.obj>