On Wednesday 31 July 2013 Jul 03:05:45 Sebastian Sauer wrote: > +2 > > May I suggest a two steps approach: > > 0) Get pending work needed for the port to master while still on Qt4. > Give them some time till problems are sorted out.
Yes -- that's wnat I'm doing in the krita-mvc-rempt branch, for instance. It's a refactoring that makes KoPart no longer a KPart -- KoView is the only KXMLGuiClient now. > > 1) Port > > Port to Qt5, keep kdelibs deps like they are, use e.g. those kdelibs > fake lib I have in coffice. Yes -- that's what is now happening in the calligra-qt5-rempt branch. Following friedrich's suggestion, I'm now focussing on libs, words, stage, sheets, active (and krita, in my spare time...). But whenever something gets ported by perl, everything gets changed. > Golden rule: Not refactor. Never ever refactor while porting. Right -- though sometimes porting feels like refactoring, when the guidelines say "use Qt classes instead of K classes". I am currently sort of stuck in sheets/localization, where there's a lot of special stuff going on. > > That's not a rule I came up with but its very very true. Just not > refactor during a port. Never ever. Get things compiling, starting up, > core functionality working, voila. > > 2) Refactor. > > Specific things will need refactoring the one or other way. This will > need much testing and has lots of potential for regressions. So, ideally > now the work should happen in master. Hm... I wonder how difficult will that be when, for instance, we need to refactor the plugin system? > > What I suggest is to do the port in a branch, get things working good > enough so people can at least start the apps, load a document, view it. > Then merge the work to master, start discussing / working on needed > refactorings. Right! > p.s. I would be willing to help on 1) and 2). that would be awesome :-). calligra-qt5-rempt is the place to be for now :-) -- Boudewijn Rempt http://www.valdyas.org, http://www.krita.org, http://www.boudewijnrempt.nl _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
