 Okay, thanks. So, yes. Okay, just a little agenda. I will speak about tools, especially for developers, newcomers, in source code. It's my friend's conference at LibreFist project and first in English. So, it's a big challenge for me. So, I'm a French community member. I live in Savoie, France, a maintenance region. I especially involved in QA. I'm a LibreFist user since StaroFist, most of the time under Linux. Working for ARAWA at the help desk, an open-source company in France, mainly motivated to understand how things work under the hood. Before, I was a teacher in electrical engineering. I have students and it was a different world for me. So, I mainly saved though about open-source topic. It's a very experimental approach. So, the goal is to share some so. Feel free to test yourself and report anything. Of course, LibreFist is a very huge database. We need tools to not feel overwhelmed with 7 million line of code, especially for beginners. Of course, we have already some tools. Remember, we have OpenGroke, a text search engine, DoxyGen, well known source documentation project, which provides HTML documentation. And of course, you can still perform any text search with your favorite editor, automatic compression, other great tool with smart regex rules. Everything is on the wiki. Okay. The story. So, I was interested to have some class diagram, a clear dependency graph. DoxyGen provide this, but sometimes it's complicated to interpret. So, I'm looking for other tools, free software. I mainly using the code on Linux. Ventation was one day called by an article about source trail. It was a project edited by a little team, a little startup, which released an open source version in 2019. So, tested in the real world. The promise. It's not an advertisement from myself. I think this project is interesting. So, the promise is get productive on unfamiliar source code. So, it's the case. There is always a part you are unfamiliar. It sounds good. This software can analyze a C, C++, Python, Java. Okay, perfect. It's not, it's, oh, sorry, there is a mistake. It's a desktop application. You no need to be connected to any cloud service if you want to keep your work secret. It's very fast to set the tools. You have two parts. You have two parts. You have to get in VS code, VS code, or the idea of the source trail program. I will show you next. Install source code and get, or get the app image. So, next, maybe you know that, compile your new graphics code. You have to run, make the idea integrations, because you create a compile.json file, which is needed by the application. So, after you select the project, you create it, and you launch the index session. Sorry, I feel. So, you need some times, because you have to index a huge source code that has some hours required for indexing, and a little space near two gigabytes. After that, you have your first screen with, on the left, all objects in the code with the number of objects. So, it's huge, of course. And on the right, you will see the source code here. It's a little summary with your seven millions of lines of code. And you can dive in next. So, you have to understand that VS code is connected with source trail and can exchange source location. So, if you point an object in VS code, you are transported, yes, at the right place in source trail. At the bottom of the menu, the context menu, you have a source trail sent location. So, what we'll see next, so, I have a little example. I'm interested to see what is in set parameters. It's in the basic directory, the basic language. You have some round box who represents class and with object in it. And the relation between a different object with an arrow and link with other symbol. You have two expanse. It's a bit contracted. We'll see next in the live demo. And, of course, there is an object which is called PMF, PMF hub, I think. So, the name is not very explicit. So, what is this? It's a private field. So, you can instantly point to it and source trail will expand. It's a type. In fact, it's a type of this field and show you what is this really. Very easily. So, that's the principle. Okay. So, now I will show you the real thing. So, it's, okay. So, I have a bookmark. I already prepared the activity. So, I have a bookmark and I am at the right location. So, we see set parameters. And on the right window, this method. Of course, I am not, if I see the VS code windows, I am not in the right place. So, it's a contextual menu. I show in idea. And, yes, yes, yes. It's the line. I am in the right place. Okay. So, back to source trail. So, I tell you I can expand any object I want to see. Okay. It works. So, I have to expand. It's, I have the type of the link type use can, of course, set the window. So, I can see what is the type exactly or other information. I can close the box and see other things. So, I go back to set parameters. I have some links to other objects, of course. I can see the relations, I think. It's not a good example. Of course, it's a point other object. I can have other view. And as you can see, the source code change accordingly. It's a very, I want to see other things. It's not, if I point to other versions, sometimes I can see inheritance. Sorry, it's too big now. So, I have to decryse. Yes, for example, you have inheritance link like this. And, of course, you can see the inheritance link in the source code. If you want to go to the idea, idea, so show in the idea and you are now at the right place. So, if I want to go back, I can use, of course, a row, a history row or bookmark. I have bookmarked precedency. Yes, that's why I'm looking for you can have other dependency graph from the sbx method, for example. It's interesting. You can see the inheritance diagram and if you need it. And, of course, you can expand to see some interesting. Okay. So, I think this tool is interesting to help a little the developer, especially beginners. It's another way to navigate in source code. So, the demo is at the end. It's a basic example. You can have, of course, many, many dependency graphs. You can, something, of course, you can move everything. If something is not interesting, you can hide what you need. And it's interesting to, you can say, if you want to illustrate any documentation. Okay. So, we stop here for the demonstrations. I will talk a little about the project. I have discovered, I have discovered it one year ago. So, it's not a replacement for the oxygen. Keep it, of course. The oxygen use commentaries in it. It's not the case here. The problem is this project is very little. It runs since 2015. And it's supported by a little team of contributors. The freeze are yesterday. Yesterday, I think of my slides and the freeze of the project is announced. And the last versions will be at the end of this year. Why? Because the team is little. And, of course, developers want to reach other interesting open source projects. So, of course, but happily, and so maybe the project will be, will have a successor. And the source is available, of course, on GitHub. Okay. That's all the moment. And thanks to the audience. Yes. Thanks, Regis. And don't hesitate. Your English is very good for talks. Thank you for the demo for the very handy example with this tool. Yes. As you mentioned, there were some comments in the chat room that quite yesterday, this freeze was pronounced for this source trail tool. So, perhaps there will be a future for it. But I'm sure that it is, it could be used at least for a few months for doing work, right? Yes, it's a question. Yeah, I asked you for your advice, if it is okay for you to use this as it was yesterday freeze. Yes. That it is okay to use this tool for the next months as well. Yes. But I think these tools can be continued. Of course, we have to talk about, because I don't know if some people know how to use it already. Okay. So, I will look at it in the next week or month, try to improve this user. It's free, it's open source. There are some other proprietary tools, but not so simple to handle. Okay. So, if there are some interested in prolongation of this tool, I think they should contact you and you can build a group for promotion. Why not? Of course, of course. So, any other questions? I do not see anything in the chat room. You have now the chance. Hello. Could you provide any alternative if this application is discontinued? Alternative. That's what I'm looking for. Just a question. I am not the developers. I'm looking. I follow a little this project. It's one way to contribute and use and speak about it. But I am not a developer for the moment. I will see the source code if I can do something in it. But that's a problem. I don't know any alternative which can handle so big geographies that others. So, for the moment, if someone knows something about it, an alternative, I can be interested. So, I don't know if it is an alternative for this special part of this tool chain. But as all know, we have this open croc tool. But as you have demonstrated, it's very handy with these shapes to click in and to go down this inheritance tree and so on. I don't know if this is possible in open croc. Thank you. If possible, I think it is good to let the developers know about it in the developer mailing list. I think this can be a good and interesting issue for the developers. Okay, I do not see... Okay, language analysis is very tricky and complex, visualizing your giant project is hard. Do you know any alternatives other than open croc? Yeah, Hossein, you asked these questions by yourself. So, other questions? If not, thanks Regis for your kind talk, for your efforts. And I hope we will hear you again the next time with your second talk in the conference. Thanks for this talk. And let me perhaps use this time between the next talk to a little advertising. As you see this shiny t-shirt here, we have delivered to every organizer and every speaker. So, if you want to have such a t-shirt of the conference, of the online conference, you can have a look at the conference website. There's a merchandising link. You can get it. This was a little advertising break for it. We have five minutes left. So, have a quick coffee. I will follow on exactly on 3.30, because the next is a video longer than 30 minutes. So, we will have not so much time for questions. If you have questions for the next talk, give it in the chat room. Hashlipokon-room1. And perhaps the Raphael could answer it in the chat room. But I will say it again a minute before the start of the video. See you in five minutes.