[Qucs-devel] Fwd: Porting to qt4 -- Please vote.

[Gopala K. <kri...@gm...>]

---------- Forwarded message ----------
From: Gopala Krishna <kri...@gm...>
Date: Aug 29, 2006 2:26 PM
Subject: Re: [Qucs-devel] Porting to qt4 -- Please vote.
To: Raimund 'Raimi' Jacob <ra...@lk...>


Hello Raimi,

On 8/29/06, Raimund 'Raimi' Jacob <ra...@lk...> wrote:
> Gopala Krishna wrote:
>
> hey folks!
>
> >>> So it is upto you to decide whether to branch or use new cvs tree.
> >> This all seems too much to call it just a "branch".  That's why i vote
> >> for a new CVS tree.
> >
> > Ya even I vote for new cvs tree.
>
> as the official CVS slave i want to add my .02 euros:
>
> the question wether a new cvs branch or tree has to be used is a
> question of how long you want to maintain both forks and how you want to
> propagate changes.
>
> i vote for just a new branch and the following procedure:
>
> - try to minimize parallel work! start migrating to qt4 and finish as
> quickly as possible, make as little as possible changes to the qt3
> branch or we all wont have fun anytime soon.
>
> - make a qt3 branch and let the development take place in the HEAD of
> the cvs (the "current" branch).
>
> - when changes need to be made to the qt3 branch, do it but merge the
> changes into the qt4/HEAD branch as soon as possible - resolve conflicts
> there. this way functional changes are made both in the qt3 and the qt4
> branch. (you _could_ propagate functional changes by hand, but that is
> error-prone and also no fun.)
>
> creating a new cvs tree doesnt seem to provide any benefit. if you dont
> merge between branches it just feels like like you were using an own
> tree. however, if you use an own tree, you cannot merge between
> branches. it's just a useless restriction.
>
> and of course: this is all theory - bevore doing all that the procedure
> should be testet. but i would do that and provide some copy&paste
> command lines with what you should do.
>
>         Raimund
>
> ps: keep in mind that you can check out different branches of the same
> cvs module just fine... you can develop in cvs/qucs-qt3 and cvs/qucs-qt4
> which in turn map to different branches in the same cvs/qucs module...
>

What you say might sound right but port to Qt4 is quite challenging. A
lot of code need to changed. We have decided not to use Qt3 support
library of Qt4. Instead we want to directly adapt to qt4. This may
take a long time since there is a  need to master some of the new
concepts of qt4. I also have some changes to current GUI in my mind
which will not be compatible with qt3.

"Therefore the qucs code may not work during this transition. "

So if everyone(developers) agrees to migration to qt4 keeping my above
quote in mind your view holds good.
--
Cheers,
Gopala Krishna A


-- 
Cheers,
Gopala Krishna A