Hi Sahil, Here are some pointers from my side:
1. Identify a KDE project you want to work on (Okular in your case), clone it and see if you are able to build and it properly. If it builds and runs, great! Else, see if required dependencies are met and paths are correctly configured or ask people in the mailing list. This would help you get started: https://techbase.kde.org/Getting_Started/Build/KDE_Applications 2. Identify the bug you want to solve (I'm assuming you've already done that) and undersatnd what the bug reporter is talking about/asking for. If you get a rough/clear idea, great! Else, ask for more clarification from the maintainers/reporters or choose a different bug. 3. Use lxr.kde.org for searching keywords in the respective projects and see which all files contain/use them. For example, for solving Bug 339370 <https://bugs.kde.org/show_bug.cgi?id=339370> , I searched for *cbr* in lxr.kde.org <http://lxr.kde.org/search?v=kf5-qt5&_filestring=&_string=cbr> and got some results to begin with. 4. Then try to understand the code of that particular function/file. If you're using an IDE, set a breakpoint to see when it's called and how it works. If you're not, improvise. For the above mentioned bug, you could see *unrar* being used somewhere in okular/generators/comicbook/document.cpp <http://lxr.kde.org/source/kde/kdegraphics/okular/generators/comicbook/document.cpp?v=kf5-qt5> and that's your cue to start playing with it. 5. Edit the source code accordingly, see if it builds and runs as expected and the bug is resolved. 6. Submit a patch. Optionally, you could mail people to review it. And that's it! Hope that helps and drop a mail whenever you need help. PS: The corresponding function/file that I chose for solving this bug might be wrong as I myself haven't viewed Okular's code before and just took a glance. It was just for giving you an example and to show how the workflow is. Cheers, Anuj On Tue, Oct 21, 2014 at 4:16 PM, Sahil Sehgal <sahilsehgal1...@gmail.com> wrote: > Dear KDE community, > I am new to KDE contribution platform and want your help in junior jobs > and bug fixing. > > I was trying to solve the junior jobs of OKULAR application and cloned its > source code into a folder. Now i am not able to decide that from where > should i start editing the source code and like which file is doing what. I > also took help from Google and found the following things, please tell > which could be the best. > > 1.) Use any IDE like KDevelop, QT creator and directly load your project > into it. > 2.) Use CMake and build that software. > 3.) Start learning the basics of KDE libraries and then look over to your > application code. > 4.) Directly look to the specific block of the code instead of looking > over the whole code, and start editing in Text editors. > > I know C++, Please help me how to understand the Workflow or how the > application works. > > Thankyou > Regards > sahil sehgal > > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to > unsubscribe << > > -- Anuj Pahuja 4th year Undergraduate B.E.(Hons.) Computer Science ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ *Birla Institute of Technology & Science,* *Pilani*
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
