Re: [Klibido-devel] kde4

[Stefan <ste...@gm...>]

On Wednesday 02 January 2008 23:25:55 Bauno wrote:
> On Wednesday 2 January 2008 23:18:25 Thomas Anderson wrote:
> > We were not necessarily thinking about a fork or anything. We just felt
> > like we wanted to start off with something that was working. We didn't
> > have any idea how much was left to do with the cvs code. I personally
> > didn't want to try and pick up half way through a database interface
> > rewrite. That was my opinion, but I am along for whatever ride. I don't
> > have the experience to be the driving force.
>
> On one hand, you're right, 0.2.5 is working (more or less) and it's a good
> starting point for a KDE4 port.
> On the other hand, the code is a real mess and should be heavily reactored
> ASAP. So it could be possible it's not worth the effort to port it.
> Ideally, the refactoring should take place before the port. But
> practically, since we don't know how much it will take, it's maybe worth to
> start the two jobs "in parallel". The KDE 4 team can then decide if and
> when port the "refactored" code into their branch.
>
> Opinions needed :-]

I don't think porting to kde4, refactoring kde3 version and then porting those 
changes is not a good idea, because refactoring probably changes most of the 
code which we'll than have to port twice.  Also, the kde4 version needs some 
refactoring, like model/view programming and I don't really like the idea of 
2 refactorings.

I put most of the changes I already made to 0.2.5 in a simple script, so it 
can be either applied to 0.2.5 or current cvs. 
I also noticed the code is messy, so maybe we can better go for a complete 
rewrite and only copy back some usefull stuff which doesn't require much 
changes. I think it will be easier this way to integrate KJove without making 
the code even worse.

Does KJove have a cvs/svn/git/... somewhere so we can look at it?

What do we do with version control? I don't care if we stick with cvs or move 
to svn or git, but I'd like to check in my changes as fast as possible if we 
go for the port.