![]() Registered Member ![]()
|
So, what would be the correct course of action to take, if I want to help get as much as possible ported to KF5?
|
![]() Registered Member ![]()
|
Do you already have an idea which application(s) you want to port? How much experience do you have with Qt4/Qt5 coding?
I guess you already have read https://kdepepo.wordpress.com/2017/07/1 ... s-porting/ |
![]() Registered Member ![]()
|
Yeah, I have read that article, thats what has inspired me to try to port some stuff over to KF5. I am not sure what I would like to do first. Whatever would help the KDE community the most I guess. Of course in particular, I liked KDE 4 better than KF5, so maybe I could start with some KDE4/KDELibs4 exclusive programs first? I do not have a lot of experience with Qt4/Qt5 coding, but I did modify the Plasma Wallpapers package a while back to include every wallpaper from KDE 4.2 all the way up to Plasma 5.8, but that did not need any C++ coding to be done. |
![]() Registered Member ![]()
|
If you have no other preference, I suggest to look at 'kget' ('frameworks' branch), 'kfilereplace', or 'krecipes'. These certainly are not as big as 'amarok' or 'kopete'.
If you have no commit rights yet, you can already start with code review requests using the phabricator link. For projects that have no 'frameworks' branch yet, we will create it. To get a feeling for the changes, check 2014 commits from https://cgit.kde.org/kolourpaint.git/lo ... hor&q=feck Porting usually starts with changes in CMakeLists.txt (see "Build with KF5" commit). It is fine to keep using KDELibs4Support for now, but porting away from it is a welcome bonus ![]() ![]() It is very helpful to check other repositories for porting commits to understand the process. If our porting documentation is not clear, you can also ask for help on the mailing list. |
![]() Registered Member ![]()
|
Krecipes would be realy nice with qt5 i have many recipes and no software to manage it.
Pls update it |
Registered users: Bing [Bot], Google [Bot], Sogou [Bot]