[kde-edu]: porting to kde4
Albert Astals Cid
tsdgeos at yahoo.es
Sat Jun 4 16:52:15 CEST 2005
A Dissabte 04 Juny 2005 16:36, Jason Harris va escriure:
> Hi Albert,
> On Saturday 04 June 2005 07:22, Albert Astals Cid wrote:
> > - Once you think 3.5 features are over and want to port to KDE 4 may
> > happen 4 things
> > - KDE 4 port made by someone else has all features you added to 3.5,
> > so you just need to do some final touchs to bring in shape
> Well, that would be great, but I think it's unlikely.
Do not underestimate the power or the comunity :-D
> > - KDE 4 port made by someone else has only some features, you need to
> > do the porting work
> > - KDE 4 port never compiled has some insider knowledge was needed
> > - You don't trust other peoples code so as YOU are the kstars team,
> > you do the porting and your code is accepted over the other people's code
> > because you are the ones that are going to work on it (this is the least
> > desirable thing obviously)
> No, this isn't about me being belligerent or territorial. The possibility
> you didn't mention is the one I think is most likely: the kde4 branch gets
> partially or completely ported to Qt4, but most of the work done in 3.5
> hasn't been ported (because as kde4 diverged, we found cross-committing our
> 3.5 features more and more difficult until it wasn't worth our time to
> rewrite everything twice).
Well, what i'm suggesting is that you do zero work on KDE4, just leave others
try, if others succeed good, if others don't succeed then you do the port to
KDE4 from scratch (or using part of the port if it is good enough). That
means you do not more work than the absolutelly necessary.
> > I don't see why you want people to stop doing free work for you...
> Yes, this point is well-taken. I am simply concerned about the difficulty
> of porting from 3.5 after the two branches have diverged. Maybe this isn't
> such a big deal, though. I'm not sure.
Teoretically branches should not diverge much, the only thing that is
radically different in Qt4 using Qt3 support layer (which lets you use
Q3PtrList, etc) is how painting is handled, painting on a widget is only
allowed during a paintEvent, don't know if kstars does much painting to
widgets outside paintEvent, in case it does i will suggest trying to stop
people doing the port as it can change code structure quite a lot.
Renovamos el Correo Yahoo!
Nuevos servicios, más seguridad
More information about the kde-edu