 and Zoltan Padrak. Welcome. Hello everybody. My name is Zoltan Padrak. I'm one of the developers of KTAC Lab. This presentation I'd like to present short history of KTAC Lab, its status and plans for the future. For me it has all started at the university, but I have been studying electronics. It was already the year of Linux desktop for me, so I have started looking for a program which could simulate electronic circuits in order to help me understanding better electronics. I have found KTAC Lab, which has been a really nice program and it has been really easy to use. It is able to show the state of the circuit, the voltages and currents in it in real time. The following video shows how this actually works. You can create a circuit, drag the component on it, and you can already see the voltages and currents. Then by dragging you can connect the components. There I'm setting the resistance of that resistor to a specific value. As you can see, the LED has turned on after being connected correctly into the circuit. If the circuit is interrupted, the LED turns off. However, at that time, also KTAC Lab could help designing programs running on microcontrollers. These programs running on the microcontrollers could be simulated together with the circuit where the microcontrollers could be used. Only the peak microcontrollers are supported from microchip. However, at that time, KTAC Lab had some bugs and it has been quite unstable. Because I have been also studying C++ at the university, I decided to help to improve the program. Back in 2008, after discussion on the mailing list and sending some patches, I have become a developer. I have found out later that the original developers of KTAC Lab have not been active anymore in the project. I do not know the history of KTAC Lab from before the start of the Sourceforge project. The first release I have been involved with has been KTAC Lab 037, back in 2009. After that, we started porting efforts towards Qt4. At the first attempt, we wanted to use the KDEV platform libraries, which are also used by KDevelop. If you look closely, you might see similarity between this window shown on the screen and the KDevelop series 4 from KDEV 4 times. And because we tried also to port KTAC Lab to Qt4, and in the same time moved a new framework, this effort showed to be very difficult and in the end we have abandoned it. My conclusion from this effort is that you do not try to rewrite software because it would take more effort than you would estimate it. In 2015, we started a new effort for porting KTAC Lab to Qt4. This time just porting towards the newer version of libraries, without modifying any functionality in the program. The only thing that has been removed from the program is the de-cop interface of KTAC Lab because that is not supported anymore. In 2017, KTAC Lab joined KDE. All the assets of the project have been migrated to KDE infrastructure. So the website has become a wiki page on KDE infrastructure. The original source for Jengitha project still exists. In 2017, the first Qt4-based release of KTAC Lab has been released. This is version 040.0. This release still depends on Qt3 support and KDE3 support, but this will change in the following releases. My plan for the future is to port KTAC Lab towards Qt4 and then to Qt5 and KDE Frameworks 5. The website for KTAC Lab has a lot of space for improvements because currently it is just a wiki page. There used to be a whole wiki as a website for KTAC Lab hosted on GitHub. That content could be reused. In the future, it would be nice to include KTAC Lab in Linux distributions and possibly distributions from other operating systems. And porting to KDE Frameworks 5 should allow KTAC Lab to be built on the KDE Continuous Integration infrastructure. Any contribution to the project is welcome. There have been always ideas for improvements and adding features. Most of these are documented inside the to-do file in the source tree. And also there is a feature request page on the GitHub wiki. One notable feature that could be added is support for mechanics in order to allow simulating complete automation systems to get together mechanics, electronics and possibly software. Also another feature that people frequently ask about is support for importing or exporting circuits from KICAD because many people use for designing printing circuit boards the KICAD software. It would be nice to get into classrooms and use KTAC Lab as a teaching tool for students. That is how I also ended up being involved in the project. For this probably it would be useful to have a portal for Windows. Thank you. Do you have questions? We have a question here. Thanks very much for taking on KTAC Lab. It's always been an impressive program that hasn't quite been able to get into the mainstream as you say. It's not in most of its distributions because it's a bit behind. I've always looked at the code base of it because I used to maintain umbrella UML modeler and we used Qt Canvas and that took some effort to be ported away from Qt 3 stuff. Can you say what KTAC Lab uses as the Canvas and what is the status of porting that to Qt 5? KTAC Lab internally uses a copy of Qt 3 Canvas inside and it draws to a PIX map which is drawn into a widget. Internally it's all inside because somebody decided it was a good optimization and porting it from Qt 3 to Qt 4 has been relatively simple because we could just take the painter code from Qt 3 and move towards Qt 4 as it has been documented by the porting guidelines. And for Qt 5, maybe the same code still could compile and run not considering it modern anyway but as long as it works we want to keep it and concentrate effort on getting it run. More questions? If not, thank you very much. Thank you. And a big round of applause. Thank you.