 My mentors were Alex Cole and David. Now, this is the basic content and I'm going to use it in a very short presentation. So, like, before this cover was, like, it does, most of the chapters are required for it to be in Plasma. You use it, but it was that in the middle of things. And after this project, because it's coming, it's merged now, FenderWits can be in the front of the UI. So, like, it's for my project goals on FenderWits by FWIT. For those who don't know, FWIT is a demand group created and maintained by Nature. And it started this project in 2015. And basically, it's a global solution implementation for FenderWits and on the other hand, backups and devices connected by USB, PCIe and etc. And also, one of my goals was to, like, integrate within the UI of this cover. So now, FenderWits are also displayed in the updates section of this cover. So, basically, my project was split into three phases. One was basically I was trying the same thing about including libraries of the Wikipedia. So, like, initially, FenderWits was very simple for me, but then I worked on the rest of that. So, basically, in phase one, I made senior files to, you know, like, so that it's easy to find out what the details are. And just to check the library of the updates, I basically completed the devices shown in the disk cover and showed it in the disk cover. In the phase two, I did some things for the FenderWits. Basically, there is no need for reviews as it shows in the FenderWits. So, I have ended that part. Implemented the Fresh Emotes for the WPD. It's like Fresh Emotes basically is after the update, but for WPD. And directed to the main update page that I was talking about earlier. And in phase two, what I did was enabling it to simply remove the Emotes on settings page. And these Emotes are basically, like, predetermined by FWPD. There are basically currently two Emotes, LPFS, the next vendor official service, and the LPFS test. And we can evaluate several of the setting page, though you have to accept the MOLA equipment, which is shown in the disk cover. And in phase three, basically, I done not much more, but I think I have improved the code, fixed things, and I finally managed to become a master. And after, when it got first, I almost, I guess, started feeling CIA business. So, I had to make a component and then fixed things, but that wasn't easy. And yeah, so, things to do. I have to test it on the real device because I was not having any access to the device, which was supported by FWPD. And more bugs after checking that. Special thanks to Andrew Strykonos. He was the one who modeled me to the KD community, and I would like to thank him. Basically, in January, he allowed me for my first patch in KD partition management, and I'd like to thank Andrew for that part, so that I was finally able to have the KD community. And thanks. And my colleague, who worked on offender recently, I would like to thank you for that. Yeah, it's a sure way to go. So, good afternoon, everyone. My name is Dilip Sankhla, and I worked on my GSOC project that is called Ocular, and my mentor was Tobias Domingler, and my project was implementing the free text annotation with free text typewriter behavior. So, in this project, I worked on the Ocular. You all know that Ocular is the KD universe of documents here, right? So, in Ocular, there is a missing annotation. We have annotations. We use annotations in everyday life, in PDF documents and all the things. But you know what? There is something missing, and that is free text annotations. Free text annotations means these are the click-to type annotations, means typewriter type annotations, right? So, we were missing that, and it was very important to our community right now. So, I worked on it, and the project was focused on implementing this missing free text annotation with the free text typewriter behavior. From free text typewriter behavior, I mean click-to type. Click-to type, or you can see Live Editing, and we needed to enter a new typewriter tool into the annotation toolbar. So, my project goal was adding a new typewriter icon to the annotation toolbar, and setting dialog to the annotation toolbar, means there should be a setting for the font color, font size, type of font, and we should set the intent to free text typewriter in the PDF, and there should be font color implementation in both Ocular and Popular. You all know that Popular is Ocular PDF backend library, and Ocular uses popular Qt5 front-end library, right? And font family implementation means your Ocular or your PDFs to support all the fonts, based on fonts plus all the embedded fonts. So, this was my phase, recording phase one, and in it, I began with the initial implementation of the typewriter annotation in Ocular. Here you can see the typewriter icon that I added to it, and here is the typewriter icon. After you click it, you can make a typewriter text. It was a pretty good test, and I wrote a typewriter text cover, you can see the intent is free text typewriter, the background is transparent, that means your alpha channel is 0, sorry, 1, sorry, 0, and you can see that this is the initial implementation of typewriter, means you are not getting any font. Here the default font is Helvetica. The default font Helvetica is now supported here, and other than that, you can see the default text is here, no font color option, nothing. So, these are the simplest implements in the first phase. Then in the recording phase two, actually I was trying to embed the GIF into it, but actually LibreOffice is not supporting the GIF, so here is the sensor. In the recording phase two, I added a font color option in the settings dialog of the typewriter tool, and you can here see the font color option, and you can select the font color, and after selecting a font color, you can make a typewriter editor like here, you can see the typewriter content, hello, with the font color view, violet, something like that. So, these are my categories phase two, and for that, I had to work both on ocular and popular, because popular supports many different color spaces like RGB, CMYK, etc. So, I had to work on, I had to work on the type, I had to get the color space, and based on that color space, I had to render the annotation in that color space. So, it was a very difficult task, and it had to be embedded in the popular code, instead of popular Qt5 front-end library. Then in the final phase, it was the time for the font family implementation, but here the problem was that I didn't have enough time, most of the time I was born into font color implementation, so I just made here an experimental page for base 14 fonts. So, here the standard fonts, as you can see, here is the text, this text is rendered in Korean word oblique, you can see the oblique text here, so here we can select all the base fonts, so these are just general implementation, general implementation, this is just the experimental code where in popular, where we can just make the base coding fonts available here only, and this is just a quite little buggy, so you can see here what's left, this experimental code is quite buggy, and we do not have proper implementation, but the code here, the existing code here that I have written can be extended and can further modified to include all the points, to include all the fonts, to include the fonts into the file, PDF file, and you can see my status report in this link if you want. Thank you, and any questions or any feedback if you want. Okay, thanks so much. Good afternoon everyone, hope you had a nice day. My GSO of 2008 was to expand the rules players in the community. This is meted by Dan B. Joji and Vincent, because the first coding was designed by the GUI and the backend of the tools and the layer settings. My main project was to implement an effective and feature-rich components for the peruse creator, somewhat like inspired from other interest and image-added components. So first of all, I implemented a layer support, which is a section, as you can see in the gym, or like, I know for sure. So the basic GUI was designed first for coding phase. The coding phase included the layer support and the tool box. The second phase started just a great experience for me. The second phase consisted of all the backend code that I did. The code was so that when you just work on beauty creator I used beauty creator and I was home so eager to expand the rules players and release. So I prepared a diagram consisting of all the things I should do and others. Then the second phase consisted of the backend code, the C++. After I started with the C++, I could link the C++ and the C++ code and then comes to the third part, which is the main part. In the third part, I just interlinked the code with the produce creator. I mean, I just linked the code with the produce creator instead of limiting all the capabilities and instructions. By the way, the project was not fully committed so please excuse me. The code is available at the GitHub. I have given the status of the code at KDE. So hopefully we can use this produce creator release including the image creator and the components. Thank you. We had four students who wanted to give a lightning talk but unfortunately there was something and he was one of the students of KDE but unfortunately he is not here. So yeah, that's it for the presentation. Thank you very much to the students.