 Okay, a few years ago, we started earlier inside KDE to fix a problem on 2D printing. Let's see if this slide passes out. When you buy the Commodore 3D printers on the market, you'll probably have this screen. Most of them came with that screen. And a button on the side that you go to the menus to manage the printer. That's awful to use. For example, I got to the printers that... The emergency stop was three submenus. So before the printer, like, start fire, plug on the... I removed the energy instead of going to the menus. So, since most of the technology is open source, let's get my script here because most of the technology is open source. And the main language that the printer interprets is open source, that is the decode file. That's this one. We can write a program to interpret those commands and send and push it to the serial command to the printer. So we... To solve... No problem, it's just I'm nervous. So we have these problems. Personally, I think that we have this technology that our open source... Starts to be open source like it's 2004 because of the patents where it starts to expire for 2D printing. And we still use our technology for LCD control, like it's very old. So what we do, we are developers, we start to build the software for that. There are some solutions on the market, but the main solution used is a closed source and doesn't work properly on all platforms. So we had a problem, so we start to build Atelier. Atelier is divided into two parts. It's AtiCore, that is Atelier Core, and Atelier, that is the interface itself. I will go, we'll make a quick over on AtiCore. AtiCore is a library. It handles all the communication with the printer. It's written pu-cutie. That was a decision that we made on the beginning of the development because we wanted to build things fast, and most of the users are Windows, so we could build cross-platform more fast if it was only cutie without the KDE libraries. So it supports most of the open source filmers. We made that like plug-ins. We have, I think, that six or seven open source filmers available on our HAPPY HAPPY website. They handle that a little bit different, so we made plug-ins for them to handle the tiny difference between them. AtiCore is separated for interfaces, so you can plug anything on it, including KML, because we already support that. AtiCore also has some read-get libraries that we use on Atelier because to test AtiCore to validate our work, we couldn't wait for the whole Atelier interface. So we made a release of AtiCore in January with small test clients, and we used the same read-get on Atelier with more content. So it also has this little read-get library. And then we have Atelier that uses cutie and KDE framework to have some part of the libraries that we are using. That's, I don't know, it's now, yeah, now it's down. Here is the face of Atelier when you open it. We are using KXML window. We are using KX Editor here for the editor, if I get my mouse, yeah. You don't want to see nothing. Yeah, now you have a decode file here that you can edit and do a manage. And edit the file, save anything that you need. We are also using from KDE, I don't remember the rest, sorry. Okay, so this is the face of Atelier. We have the welcome screen that goes down. Well, you have a quick connection guide. We get the news for our website and get involved. We have the 3D view that needs work, that handles the decode file, the editor, and the camera, if I get in there, will show my face. Yeah, I'm here. I didn't test it, but since I'm using QT multimedia thing, we can use UDP connection to get our remote camera to use it, but I didn't test it. Let me stop this. So, as you can see, this side is the general read guide that we can use. We separated the work space, like two work space here. Here is the generic key that is common, features that is shared with the application. On this side, we have an article instance read guide, tabs. Atelier is the first printer host that allows you to control more than one to the printer at the time. So, here I can open any windows, and connect, if I have enough serial ports also, connect any amount of pieces that I want to and control them in each one in one session. So, this is the first printer host that allows that because of the complication. This separation from the article of Atelier. It is also that we want to reach another device, like embedded one, so it's always better for us to make this separation. The first thing that you saw is this log entrancy that when you open the stock, the port, maybe you have some trouble, so you'll see the log so you can send to us all the bugging information. I don't have it to the printer here because Thomas wasn't able to get it to the printer here today, but tomorrow we will have that. So, I have my Arduino with a firmware on it so I'll connect and show you the other side. We have these, we have auto-detect of the ports, of the plugins. When I connect the printer, I send a command, a gcode command that vertons me a huge string where I do a reject to see which firmware is that so I can load automatically the plugin. So, I'll change the profile here. So, I can hit connect. We'll be fast. Okay, now it's done. So, it's quite fast with the profile. I have a profile dialogue to add profiles because you can have an amount of printers and they'll have a lot of materials for that so you can have a profile for each material. And we have this maximum bed and hotend, temperatures that go direct to the dial to keep you away from not burning your house, for example. Yeah, because the printers can get on fire so we try to avoid that. And we have some nice features like a post-pause command when you have a decode file and if you want to pause the printer to change the filament, for example, and your decode wasn't sliced to have that pause, you can add a custom command and pause command and then when you hit pause, Atucara sees that you have a custom command and you use that instead of the default one. Atucara also allows you isn't on Atelier yet because it needs some work but Atucara today already supports decode injection also because you don't need to get to the work to re-slice your file, it's slicing easily and you get the STL object where it passes it to a program that turns it into decode so it already has the decode injection but isn't here yet. So you choose as you get the port right here, let's connect here, you get the port and get the profile and then you connect and that's the log. Hey, connect again, okay. So we have these two main dials that is the bed and the hot end one. Here we have key charts with the graph, key graphics view to moving the axis, buttons to general control. Today we have the basic control of the printer done so you can manage most of the fixtures but if your printer has a little bit difference of femur because it's open source so you can get the femur and add this stuff for you so we can support that on Atelier also. We have some advanced tab here where you can see the log. We log everything that goes out and come from the serial connection so we have like M105 that gets the temperature so we do our rejects on that to get the temperatures of the bed and of the extruder. You can push colon and control other stuff. You can also manage the SD card files you can print for that, get a list and delete basic management of the SD card. So that's it for now. We have a lot of work to do I think that this interface isn't good enough because I also think that I want to bring the best experience to my user and I think that we still have a lot of work to do on Atelier to get to a good state because I think that KDE has all these things about giving the user a good experience and has the vision to conquer all the viruses. I won't be able to do that with Atelier if I don't give the user a good experience in platform. So I think that needs some tweaking before launching. I was hoping to launch during Academy but I was able to finish the code. I hope that later this year we'll be able to we are already working on Articore 2.0 that's almost ready to launch too and following probably atelier. Tomás did this one and this nice. Yay! Just showing that I send it so the graph will be up here at the orange line. Atelier has a cute application with a multi-platform. We have here Linux, Windows and OSGs. The Windows user I met him a couple of weeks ago and how I want to test it so the guy downloaded the binary and started to use it and gave me a good feedback and they're paying the control and to the printers at the same time because I attend some events of 3D printing industry and the companies want to be able to control more than one printer at the same time because they have farms of 3D printers. It's hard to manage each one of them because a printer host is used to ease the life but people that have advanced discus don't want to get binded to a computer so they want a embedded device or a way to control remotely so it's kind of the work that we'll focus now giving us a core web layer so we can connect remotely and work on a KML version for the interface but this all thing already works and thank you to people from KDE Windows we have the binary factory running Jenkins that has master builds for Windows and OSsheets Linux we have the flat pack that one of the developers made and we have master nightly builds from there we are working on the FMAJ script but we are using Flutter FCI to build it so it's good that we already know that it's being used so Windows use the download that fact there and start to test for us and last 31 July Atelier made 2 years so we had at the core release at the beginning of this year until today we have more than 100 downloads 5th of the for Windows 44 for IPmage and the 64 OSsheets this running atelier in other platforms the Linux was a worry since the beginning of the project because most of people wanted to print and use Windows I can't force them to move to Linux but I can't so that was our main concern since the beginning so when craft the Windows and OSsheets build with craft so since the beginning we got in order to make craft to work build atelier and atcore correctly so we could use atcore has and atelier has this number of comments I'm trying not to say them and I'm glad that I'm proud of these 2 years and I can't forget to thank the people that is working with me that that will be Patrick Pereira from Brazil he is a contributor for KDE most of us are developing lately and Chris is a teller that is from New York and Thomas for guiding us not to kidding each other during the development of atelier ok any questions here great talk thank you I have a 3D printer at home how do I know if it's supported or are all 3D printers supported or is there a list ok most of the 3D printers have the firmware open source we have let me open la la la we have here the auto detect we have the plugins here so we support Tia Cup printers moffer, repeater, malin jbl this is the firmware that we support that are open source there are 2 printers that are closed source on the firmware and they use gcode 2 or they use another fork of gcode so we don't support them because they are proprietary and I don't have access to them but most of the printers that you buy from China anyway it works do you know the model of your printer yeah it works yeah I think that Annette is maling Annette I think is maling so probably work and it's if it's from China we work only the proprietary ones that won't work only if they give us money to build the support anyone else? I wanted to ask about the video feature I don't have a 3D printer so is that just supposed to watch the 3D printer as it prints because let me play this again the most wanted feature for anyone that has a 3D printer is to not depend on the machine to use what they want I embedded the version to try to connect to the printer so when you leave the printer alone printing you can connect to that server and get the feed of the printer to see if the model is printing right so we have this feature to if it's from any printer alone but is that because the monitor is a printer because there is one printer hose that is an open source that is called Octoprint that is for embedded device you put the server Octoprint on a Raspberry Pi and you open your connection internet for outside your house so you can connect to it and get that so we also have this kind of feature because people will want to use that embedded the industry wants to get embedded device they don't care much about the version but I want to hit the math that depends on computer and it's getting into 3D printing any more questions? yeah but I I didn't test it but I think that you can add you you are here for remote camera and it works because of cutie stuff yeah you are ready to pair connection you can access a remote camera but this is only for monitoring with a telephony or desktop because we don't have the web layer yet what are you using for the 3D view is it like Q3D? yeah Q3D but the when Patrick did this one was on like alpha or better version of Q3D so we needed to rewrite this and I already invoked the KDAB Q3D man to go to the old buff this week to build it and one curious thing about Atelier is that when you are running Atelier and printing the consumer of memory is around 100 megabytes of memory my main concurrent that is the one which calls it source 2 gigabytes of memory yeah C sharp so we have this advantage you have been C++ and QT that make it all life so much easier during the development anyone else? here we are any more questions? right there is one guy over there too let's take this question here I have a question regarding the preview so the GUI itself is QtWidgets based right? yeah okay how did you implement the preview with OpenGL or did you use Q3D? Q3D yes the source code is on KDAGit you can get layer you can also get onto my channels let's put it we will hold both these Wednesday if anyone wants to come please come we need more developers and we will discuss this stuff sometimes we will be with us and these are our channels you can get us there all the time and she has one last question he is coming and we have a last question thank you I have a very functional question where you are in the features of Atelier compared to the commercial software yeah when Atelier started because of the proprietary software the name of the software is Repetier Host they were open source until 3 years ago on the Apache license and then they closed the source but the program is still awful but Repetier is used because I think that was the first one and everyone says that you used it so I'm not making so much fuss about Atelier yet I have contacts with people in the printing industry when Atelier evaluates and indicates to people and I think that we can do a better job because Repetier is really awful Repetier only runs over mono and they have an object to see version for EOS that completes the interface so I think that I can get points to have a common interface and get into the industry but the math I think that people that enter into the printing can use Atelier but people that are already advanced in skill they don't like to use a printer host put the code on the SD card and hit print but they they talks that I have with people on the industry people factories that make it through the printers in Brazil for example they like Atelier because it's open source and what's to us they want to embed Atelier on their printers just because open source is one of them and they don't want to pay like 20 euros for license for machine and in a Repetier server opens a browser inside the Raspberry Pi and the two keys stuff is awful and we have KML that can give us a huge good experience on the device and I hope that on the industry that will work at least if I get this Atelier embedded on the main manufacturer in Brazil that we are discussing this is our channel you can contact us there I think that I made a good talk I want to thank you KDE for giving me the opportunity to come to my first academy and do my first talk a lot of first today and I mean okay, I can't say thank you very much tomorrow we will have the 2D printer we will print KDE keychain so anyone can buy it tomorrow I hope so and I will be there in this week so you can reach me out alright, thank you and now we are going to have a couple of minutes break and then we are going to continue with KDE