WEBVTT 00:00.000 --> 00:14.080 All right, thanks everyone for joining us, thanks for everyone who is coming on in the room. 00:14.080 --> 00:19.120 Again, if you are sitting at an edge and see you soon next year, certainly make some friends. 00:19.120 --> 00:22.280 We're going to cram everybody in as best as we can. 00:22.280 --> 00:28.600 Welcome to the open hardware and CAD CAM Devroom and Fossilum 2026, our next speaker is York 00:28.680 --> 00:30.200 from the FreeCAD project. 00:34.200 --> 00:36.840 Hi, is this working? 00:36.840 --> 00:38.440 Yes, okay. 00:38.440 --> 00:41.800 So, welcome, thanks for coming. 00:41.800 --> 00:50.680 I will do a talk about FreeCAD and basically what's new in FreeCAD, what's new in the community, 00:50.680 --> 00:54.440 what's new around the project. 00:54.760 --> 00:59.560 I'm York, that's me, I'm an architect by trade. 00:59.560 --> 01:05.480 I'm a FreeCAD dinosaur, I'm with the project almost since the beginning. 01:05.480 --> 01:14.040 I care mostly, I take care of the Bing, worry-bange, the draft a little bit still, 01:14.040 --> 01:21.640 but it's mostly in other hands now, we have to deal with my old crappy code from 20 years ago. 01:21.720 --> 01:29.160 But I'm also the chairperson at the moment of the FIA, which is the non-profit we have built around 01:30.200 --> 01:36.680 next to FreeCAD, because we made especially to not be on top of FreeCAD, but to be a side thing of 01:36.680 --> 01:41.800 FreeCAD, so the community stays in control of the project. 01:41.800 --> 01:45.320 And that is a picture of my baby and you have to look at my baby. 01:47.080 --> 01:48.440 And that's where to... 01:51.640 --> 01:57.240 And that's where to find me online on the internet. 01:57.240 --> 02:02.440 So I will talk about the fresh new release of FreeCAD that we will have 02:03.480 --> 02:11.400 hopefully soon out, there is like one more big blocking bug to fix and it should be out. 02:11.400 --> 02:16.840 So I won't say anymore when, because last time we say, 02:16.840 --> 02:22.280 don't always next day, next week, and then it takes for more, but it's pretty soon. 02:23.400 --> 02:30.120 So I will show a bit of what's in this version here, and also a bit of what developers are working on, 02:30.120 --> 02:35.800 what the community is doing, and a bit of FIA news, what we're doing with the non-profit 02:36.920 --> 02:38.760 next to the project. 02:40.040 --> 02:43.560 So that's a screenshot of actually FreeCAD1.0. 02:43.640 --> 02:48.680 I use it just to basically say that FreeCAD1.1 is the same. 02:49.720 --> 02:54.680 Basically, it's meant to be bug fix release before anything else. 02:55.640 --> 02:58.840 So for 1.0, we really rushed a lot. 02:58.840 --> 03:05.640 We wanted this 1.0 to be the next big thing out there, and we had to put some stuff there 03:05.640 --> 03:13.400 that we really wanted that mattered, like the assembly workbench or the system that we have 03:13.400 --> 03:16.120 to fix, what we call the top on a main problem. 03:16.760 --> 03:23.720 That number of reference would change in your model, and then something would change positions. 03:24.600 --> 03:30.200 All these things were really rushed into 1.0, because we had to do it. 03:30.200 --> 03:33.960 It took so long to get there, and we had to get it out. 03:33.960 --> 03:37.640 But there were a lot of instability. 03:37.640 --> 03:43.720 So after 1.0, we sit down, and we go slower, and we fix things. 03:44.280 --> 03:51.720 And that was in many levels, the code itself got work on it. 03:52.440 --> 03:58.440 But also the process that we had, we were trying to put more human testing into things. 03:58.440 --> 04:05.320 So when someone writes a new feature, we said, OK, let's wait until someone not only looks at the code, 04:05.400 --> 04:11.560 but also runs, we kept with it, and plays with things, and make sure things don't break. 04:11.560 --> 04:19.640 It's also all our process went slower, and better, and we believe all we're pretty happy with the 04:19.640 --> 04:28.840 stability that we gained back, I hope, when you get your hands on this, you will find the same. 04:28.840 --> 04:31.480 But basically, things are the same. 04:31.560 --> 04:35.720 It's the same old-free candidates, where to the same things are the same place. 04:35.720 --> 04:41.080 Only only things that may be used so crashing when you were using 1.0, 04:41.080 --> 04:46.760 that this floating panels would vanish, or wouldn't work with wayland, etc. 04:46.760 --> 04:58.840 All the things got a lot of work on it, and all of this got hopefully much, much, much more stable than 1.0. 04:59.800 --> 05:10.040 A bit of frequent porn, of course, a nice image to allow, and there is this forum section where 05:10.040 --> 05:17.720 people can post what they're working on, and it's always a nice place to have a look for nice 05:17.720 --> 05:24.360 stuff people are working on. Hope you all went to our table there, there are crazy machines, 05:24.440 --> 05:30.600 spaceships on the table, so make sure you go there, that there is real stuff to look at. 05:34.200 --> 05:41.080 UI improvements, there are a series of improvements to the UI, all of a freecat. 05:42.120 --> 05:49.160 We have a new team editor, teams, the teaming in freecat is still a bit of a mess with a lot of stuff 05:49.240 --> 05:56.680 everywhere. We're trying to slowly go towards a kind of easier way to change the teams, 05:56.680 --> 06:05.560 and to define custom teams without having to tweak hundreds of parameters, and so we have two basic 06:05.560 --> 06:12.440 teams, like one and a dark one, and you can tweak certain colors, and this is getting easier 06:12.440 --> 06:22.200 to get a team like you want. We have a couple of flighting improvements, three-point flighting 06:22.200 --> 06:28.440 editor, where you can tweak the position and the color of the lights, and we have a lot of work 06:29.960 --> 06:36.360 regarding custom properties that you can now add to just any objects in freecat, and 06:36.360 --> 06:45.000 you have much better, much easier dialogue to do. You right click on an object and you add new 06:45.000 --> 06:51.640 properties to these objects, for who doesn't know much about how that work, basically you can 06:51.640 --> 06:57.400 add new properties to objects, and you can have other objects refer to those properties. So you 06:57.400 --> 07:06.040 say basically, okay, I have a cube, but I once had a density property you added, and then you 07:06.280 --> 07:14.040 can have other objects refer to that density value to do something. The height of the 07:14.040 --> 07:18.920 other object depends on the density of this one of whatever. That's the beauty of freecat is that 07:18.920 --> 07:26.360 the parametric relationships that you can create is your decision. You go wherever you want, 07:26.360 --> 07:33.480 and you plug whatever you want into whatever you want, and you define your structure, and your model, 07:33.560 --> 07:46.680 the way your wild imagination can get you. That's the most interesting part we had in the visual 07:46.680 --> 07:54.120 aspect of freecat is that there has been quite a lot of work on what you see on screen, the manipulator 07:54.120 --> 08:02.120 that you see on screen on the left part is the transform tool that you use to move an object or rotate 08:02.200 --> 08:08.920 or scale it. This is no much better, you can click on the different part of this manipulator, 08:08.920 --> 08:15.880 a bit like the one in Blender. It's getting where we would all like to have, it's like you can 08:15.880 --> 08:23.480 really manipulate this thing precisely. On the right side, that's the result of Google Summer of 08:23.560 --> 08:33.400 codes of project of this year. Basically, this is used in a couple of parts design objects, 08:33.400 --> 08:40.840 but of course the idea is to widespread that's everywhere. In freecat is basically, in this example, 08:40.840 --> 08:52.520 you can drag the red arrow and you change the extrusion depth of the object on the object, 08:52.600 --> 08:58.200 on the object itself. This is tied, of course, to the property, you see, it changed when you drag, 08:59.000 --> 09:07.800 etc. And this is really, really nice to use, and this is solid, this work well, this is well integrated 09:07.800 --> 09:14.440 in the rest of the freecat, so this is basically a test bed for, so to me, spread this around as 09:14.520 --> 09:23.560 much as we can. In bin, we have a couple of new things. I have personally not worked much 09:23.560 --> 09:34.920 on bin because reasons used so earlier, bin busy, but we have a couple of improvements in solar 09:35.000 --> 09:43.880 solar studies, you can place the sun and define the sun positions more accurately, 09:43.880 --> 09:49.720 and we have a new solar world bench that can perform lots of calculations based on that, 09:50.520 --> 09:58.440 and that kind of opens the door for more complex energy simulations, etc. Which is a big, big, big, 09:58.440 --> 10:04.200 complex area, and there is no easy way into it, but that's where we would like to arrive at 10:04.280 --> 10:10.120 some point to be able to really perform from freecat energy analyzes in bin. 10:11.880 --> 10:19.640 In can also, you have lots, lots of new parts we don't, nice, new tool, library manager, 10:21.000 --> 10:30.120 with lots of presets, the editor is also new, still some glitches here and there, 10:30.200 --> 10:37.400 but this is nice, there is really a lot of improvement there in can, and that's one of the 10:38.440 --> 10:43.160 modules that's got a lot of works recently, and there are many new developers, 10:44.040 --> 10:50.520 one of them is now a member of the FPA, and there is a lot of activity around come, and 10:50.840 --> 11:00.600 FEM to be honest with you guys, I don't know nothing about FEM, so I just took a couple of 11:00.600 --> 11:08.920 sexy sci-fi looking image and I put them here for you, but basically there is a block post, 11:08.920 --> 11:14.280 only about that, so if it's your thing, I would suggest to go to the freecat blog and look for FEM, 11:14.280 --> 11:25.640 and read the overall blog post, it talks basically about this, and how you will begin to use FEM 11:25.640 --> 11:33.960 for electromagnetic analyzes, and other electric 20-perlated subjects. 11:34.840 --> 11:45.960 In part design, we have a couple of new stuff on the interface, this new whole tool, 11:45.960 --> 11:57.080 and this is the kind of work where the, we have a group in the freecat 11:57.080 --> 12:05.240 that takes care of design, and they've been very active about this, and they're like 12:06.760 --> 12:13.960 writing guidelines for writing interfaces, and this is the kind of direction we're beginning to 12:13.960 --> 12:22.360 steer towards, to have more of this kind of work on the interface, and so it's begin to appear, 12:22.360 --> 12:28.120 begin to be out of only in papers and begin to be implemented and freecat, and you begin to be 12:28.120 --> 12:37.160 able to see that in part design. There are improvements over threadings also, and one of the 12:37.160 --> 12:44.840 nice things is that you have transparent previews, when you're still in the creation panel, 12:44.920 --> 12:52.280 and you change the parameters of a whole that you're making, you see on the industry 12:52.280 --> 12:57.160 review where we'll be where the whole will be, etc, and you've changed the parameters, 12:57.160 --> 13:02.760 it updates, of course, in real time. So before you press OK, you see the what you're doing. 13:05.320 --> 13:12.040 The sketcher also has improvements, basically a couple of new ways to attach 13:12.040 --> 13:21.000 X-term geometry or to use X-term geometry inside your sketches, which is always a complaint that 13:21.000 --> 13:26.600 we hear that's not very easy to use geometry from other objects, and for example, you know 13:26.600 --> 13:32.600 have a projection tool, so you can use projected geometry from an object that's not directly 13:32.600 --> 13:41.640 under under your sketch, or the section tool where you can with the plane use section to an object 13:41.720 --> 13:51.400 as a reference for another sketch. There is much more actually, I should have also put some more 13:51.400 --> 13:59.880 sketch porn here, with like those magnificent sketch full of constraint. We'll remind for the next time. 14:00.840 --> 14:14.520 The wiki has also seen a lot of improvements. We used to, we had the internal discussion, 14:14.520 --> 14:20.840 if we get out of the wiki or not, and the frequent contributor confusion put a lot of work 14:20.840 --> 14:26.680 into the wiki and we're staying with the wiki now, because it's nice now, and it has a lot of 14:26.680 --> 14:37.320 things that we want, it has a good synchronization, it does back up, it has a better search engine, 14:37.320 --> 14:43.240 and it's something that's working pretty nicely. There is much more everywhere, so I would 14:44.040 --> 14:49.560 suggest you guys to refer to the release notes, the frequent blog, the master of the three places 14:49.560 --> 15:00.040 where we often put out what's new, over these other areas that got improvements. 15:01.080 --> 15:07.320 What's cooking, what's our developers working on? We're working on new websites that would integrate 15:07.320 --> 15:15.480 the blog, all those little pieces of stuff that we have around would be inside one CMS, and 15:16.440 --> 15:25.800 so that's something, this is not the aspect of it. We'll look at the aesthetics later, 15:25.800 --> 15:31.000 now we're just working on making it work and having all the features that we want. 15:32.040 --> 15:40.040 The lens server is a file server that was created by Oncel, which is a company that's last year 15:40.040 --> 15:48.600 was still there, and they made this commercial version of Riket, a fork of Riket, that they were 15:48.600 --> 15:57.480 developing, and the development was this file server. The Oncel company died, the plot was removed 15:57.480 --> 16:05.480 from them and they lost their funding, so they shut down, but all the assets were transferred to us, 16:06.440 --> 16:12.200 so that's a really, really cool thing that's happened, and we got massive donation 16:14.040 --> 16:19.880 to help us, an anonymous person, gave us a very big donation to help us, 16:20.760 --> 16:27.000 turn all these assets into something usable, that is refining them so they can be used by everybody. 16:27.000 --> 16:33.160 They are deployable, they are installable everywhere, etc. So that's happening now, and so it's not 16:33.240 --> 16:41.640 the Oncel lens server anymore, it's the Freak at Lens server. We have Joe there working on 16:41.640 --> 16:47.800 new learning material, hopefully something that we would be able to distribute to universities 16:47.800 --> 16:55.320 and try to help Freak at to enter universities, etc. We have work on people working on 16:55.400 --> 17:04.760 multi-training. I won't read this because I don't know much about it, and it's still pretty 17:04.760 --> 17:09.800 much working progress, but those are things that are worked on. The rendering pipeline, there's 17:09.800 --> 17:17.320 lots of people working on the coin render, looking for other ways to improve the rendering. 17:17.400 --> 17:25.400 This is something being worked on. Text tool for the sketcher, there is another one that is 17:26.280 --> 17:31.400 concurrent one that is not only for the sketcher, but for textiles. Also, we are looking at 17:31.400 --> 17:38.680 there are various efforts coming in, and this is all being in the process of being integrated. 17:39.320 --> 17:47.800 Around the community, we've done good homework to. We now have all those regular video meetings 17:47.800 --> 17:53.560 that we have. Every week, the FIA has a meeting, every week we have a merge meeting where we 17:53.560 --> 18:00.200 discuss collectively what's gets merged, what doesn't get merged. Every month we have 18:00.200 --> 18:06.760 developers meeting where anybody is welcome to come and talk about what their issues with 18:06.840 --> 18:15.080 development is. All this is annotated, we have minutes, everything, all of this is public, 18:15.080 --> 18:22.360 so we have like good record of what's happening during these meetings. We have a frequent hand 18:22.360 --> 18:28.200 enhancement proposal system, which is beginning to work very well, it's like if you're planning to 18:28.520 --> 18:36.680 make big changes in FIA, now you open your right paper over what you're proposing to do, 18:36.680 --> 18:43.480 and other developers maintain a scum comment and that way we can, the developer himself 18:43.480 --> 18:50.120 has better insurance than when they will begin to work. They won't be people coming. What are you 18:50.120 --> 18:57.160 doing? Stop now, we didn't agree with that, so there is all this process of having people agree 18:58.040 --> 19:04.280 to what's going to happen and that helps things to go further. The key connects, 19:04.280 --> 19:11.480 probably most of you must have seen this this morning, is like a thrilling effort connecting 19:11.480 --> 19:21.080 keycats and a couple of more slides on the FPA, so the FPA, as I explained to you, is a side 19:21.080 --> 19:28.200 body of a breakout, it doesn't comment on breakout, it doesn't comment on anything, 19:28.200 --> 19:34.600 else than its own money, and its use, its money, it has different members, many members of the 19:34.600 --> 19:40.680 FPA are also developers of the breakout, but not all, and FPA basically has money that the 19:40.760 --> 19:48.840 committee gives and it decides where it puts these money, and we have kind of stable income, 19:48.840 --> 20:06.120 my more or less, 1,550,000 Euro per year, and with that, we basically find in the couple of programs. 20:06.120 --> 20:12.040 One is the grants program where developers want to develop something that would need the 20:12.040 --> 20:18.520 couple of thousands here to do that, they come to us, they may build a proposal and we give 20:18.520 --> 20:20.840 them money to do that. 20:20.840 --> 20:27.880 We have a couple of fixed positions, people who earn money monthly from Fricad and those 20:27.880 --> 20:32.880 are basically roles that we want to benefit everybody. 20:32.880 --> 20:39.520 So there is one who is doing bug 3-age, there is one who is taking care of the Adam system, 20:39.520 --> 20:45.560 the Adam developers that are up to date with the development of Fricad, that kind of things 20:45.560 --> 20:49.960 roles that benefits the whole community. 20:49.960 --> 20:56.160 And we have also another program we show that now for a specific for bug fixing. 20:56.160 --> 21:02.480 And again, we're trying to put that money not directly into development because development 21:02.480 --> 21:07.920 is still in the hands of the community, it's the people, the users who have to develop 21:07.920 --> 21:15.960 Fricad and that we find that it's very important that it's made by its users mainly. 21:15.960 --> 21:21.560 So we try to use this money to help developers to develop basically. 21:21.560 --> 21:26.160 In some ways that benefit everybody. 21:26.160 --> 21:34.240 We now have a new bug bounty program that's from last year, basically you fix 5 non-bugs, 21:34.240 --> 21:40.480 you can claim or reward and if you fix more important bugs like critical bugs for the release 21:40.480 --> 21:45.560 or something like that, you get more money. 21:45.560 --> 21:52.720 This started this year, we were very careful with bounties, we thought it's somewhere 21:52.800 --> 22:00.120 very highly critical of it, but after one year, I think we love it, it's working well and 22:00.120 --> 22:07.400 people are all developers are using it and it's really gluing something in the community 22:07.400 --> 22:11.640 and it's working really nicely. 22:11.640 --> 22:18.720 And finally we have new positions that is people who are paid monthly over the year. 22:18.760 --> 22:28.280 We are a Peter, as an OCT liaison, he makes the thinking with the OCT project which 22:28.280 --> 22:34.600 is the kernel of Fricad and we needed someone to go there to report a bug's upstream 22:34.600 --> 22:38.920 and to make all this communication between the two projects. 22:38.920 --> 22:45.520 We have someone now taking good care of our web infrastructure and people to work with 22:45.600 --> 22:56.120 the atom ecosystem that we want to be a bit bigger and a new financial officer that's taking care of the money. 22:56.120 --> 23:01.520 I guess that's it, thanks for listening and happy to answer your questions. 23:01.920 --> 23:04.920 Thank you. 23:09.920 --> 23:16.920 Hi, my question is why would you be initially critical of bug bounties? 23:16.920 --> 23:19.920 Like what would be the reasons for Chris? 23:19.920 --> 23:28.520 The main resistance at the beginning is that we wouldn't think of bounties as something we would pay for. 23:28.920 --> 23:37.920 We would think of it as like traditionally people would put money on stuff and we thought this can derail easily to. 23:37.920 --> 23:46.920 Lots of people putting much money on something and that something is not done and then we will get whole kind of people. 23:49.320 --> 23:56.720 Not happy about the world thing and won't be a nice experience and we have a lot of example of things like that. 23:56.720 --> 24:07.720 But then we made our own program, we decided how much we would put into this and this is working really nicely and so it has the same name but it's really our 24:07.720 --> 24:17.720 our bounty system and nobody is able to direct to put money on it and I think that's what maybe what makes the difference. 24:18.720 --> 24:20.720 Thanks. 24:25.720 --> 24:28.720 Hello, just related to the bug bountie again. 24:28.720 --> 24:34.720 Did you see many people just submitting murder requests made with a bit of AI slot? 24:34.720 --> 24:37.720 Just to get the money or had to do with it? 24:37.720 --> 24:38.720 No. 24:38.720 --> 24:39.720 No. 24:40.720 --> 24:57.720 We had a couple of AI slot but it surprisingly the last ones are good quality of people who know what they're doing and I was the opinion that we never will have AI in frecad. 24:57.720 --> 25:16.720 And we're about that question we're still looking into it but things are really changing and so far it's mostly the developer themselves who already developers who went to the bug bountie program. 25:16.720 --> 25:34.720 Yeah, I had a question maybe I'm not familiar with the governance of your project but do you have any sort of CI loop or some way to sort of know that the merges are not actually breaking sort of known designs and whatever else like a standard set of like I don't know 50 or 100 designs that are really complex and see if every version of bug great actually is able to properly. 25:34.720 --> 25:36.720 I didn't get three in your question. 25:36.720 --> 25:43.720 I mean so one of the things that we each up struggle with frecad is we have some complex stuff that we're loading into it and sometimes it struggles with it. 25:43.720 --> 25:53.720 And we're not exactly sure if it's the computer the person is the free ads having a problem or so we're just wondering if you guys have some sort of you know kind of poly insurance that goes on. 25:53.720 --> 25:55.720 Quality checking somehow. 25:55.720 --> 25:57.720 Yeah, that's so automated like every every upgrade. 25:57.720 --> 26:09.720 Yes, one of the things we improved this year and we now have a massive unit test system that you can write unit test for almost anything that happens in frecad. 26:09.720 --> 26:13.720 We ask people developing new features when they submit the pull request. 26:13.720 --> 26:18.720 Please write a unit test to test automatically test your feature. 26:18.720 --> 26:21.720 That's a bettering a lot. 26:21.720 --> 26:24.720 So we now have a lot of testing. 26:24.720 --> 26:31.720 And if that's really a factor in the stability, I don't know. 26:31.720 --> 26:35.720 It doesn't harm certainly to have a lot of unit testing. 26:35.720 --> 26:41.720 But I would say we're trying to better in testing in all matters. 26:41.720 --> 26:44.720 Not only automatic testing, but also human testing. 26:44.720 --> 26:47.720 That's something we have done too fast in the past. 26:47.720 --> 26:48.720 We've just merged. 26:48.720 --> 26:50.720 Okay, it's passing the test. 26:50.720 --> 26:51.720 It's good. 26:51.720 --> 27:03.720 And now we stop and we say, okay, this will only pass if someone, if a human comes here, compiles the thing test and try to break thing and make sure it works. 27:03.720 --> 27:09.720 So it's a bit slower pace, but I think it has helped stability a lot. 27:09.720 --> 27:27.720 Thanks for the presentation. 27:27.720 --> 27:32.720 So maybe it's not completely focused on frecad discussion. 27:32.720 --> 27:36.720 My question is, what do you think about the current state of card format? 27:36.720 --> 27:44.720 So is the best kind of open format the step 242? 27:44.720 --> 27:46.720 Is it good enough? 27:46.720 --> 27:54.720 Or frecad can play a role in this scenario, which is very fragmented, let's say? 27:54.720 --> 27:56.720 Yeah. 27:56.720 --> 27:59.720 It's a hard question. 27:59.720 --> 28:00.720 I don't know. 28:00.720 --> 28:05.720 I think step is proving to be there to stay. 28:05.720 --> 28:08.720 And it's still widely used. 28:08.720 --> 28:13.720 What we can see around the frecad community is step is paramount. 28:13.720 --> 28:14.720 Step is everywhere. 28:14.720 --> 28:17.720 Step is what everybody uses. 28:17.720 --> 28:21.720 Step is the step exporting important frecad is actively developed. 28:21.720 --> 28:23.720 So people are working on it. 28:23.720 --> 28:25.720 People are making better. 28:25.720 --> 28:30.720 When you import a step, you have more and more complex model that comes out of 28:30.720 --> 28:31.720 their instead of one object. 28:31.720 --> 28:32.720 You have all the structure. 28:32.720 --> 28:35.720 You can remove the pieces, etc. 28:35.720 --> 28:40.720 So it's certainly something the community values and works on. 28:40.720 --> 28:49.720 Now it's a bit of a weird landscape where big vendors are pushing the things to their sides. 28:50.720 --> 29:01.720 Whereas as an open-source project, we don't have much act possible actions aside from watching them fighting. 29:01.720 --> 29:10.720 And personally, my course of action is always to stick to open formats. 29:10.720 --> 29:14.720 And that's basically our kind of salvation. 29:14.720 --> 29:20.720 The more we can keep track of our own data, we can know what's in our files. 29:20.720 --> 29:25.720 We can store things in things that will be openable in 20 years. 29:25.720 --> 29:31.720 I feel we are safe track. 29:31.720 --> 29:40.720 So yes, inside the frecad universe, we stick to these things, basically. 29:40.720 --> 29:50.720 What are your thoughts and opinions on the DXF and DWG format in relation to open source and the support that we get? 29:50.720 --> 29:57.720 That's a cool question because it comes back since the last 20 years, right? 29:57.720 --> 30:01.720 That we are having these kind of questions. 30:02.720 --> 30:10.720 For those who know the DXF and DWG are property formats from Autodesk that are used back in AutoCADs, 30:10.720 --> 30:15.720 but why they spread around the engineering community. 30:15.720 --> 30:20.720 Everybody use these formats up to today. 30:20.720 --> 30:29.720 You have a couple of open source projects like a library that's trying to crack it on the format to bring it to the open source side. 30:29.720 --> 30:32.720 It's still being always watching that project. 30:32.720 --> 30:35.720 It's still being worked on, it's still being committed every week. 30:35.720 --> 30:39.720 So it's still active and still people believe in it. 30:39.720 --> 30:42.720 So it's not that and it's there. 30:42.720 --> 30:46.720 It's hard to use at the moment. 30:46.720 --> 30:49.720 DXF is something is the open version of DWG. 30:49.720 --> 30:51.720 DXF has text inside. 30:51.720 --> 30:56.720 And DXF is something wide used and we can use and we are using. 30:57.720 --> 31:00.720 It's easy to use in frecad and it's solid. 31:00.720 --> 31:02.720 It gives good results. 31:02.720 --> 31:13.720 DWG, we're still waiting to see where this goes, but what I can see is that it's still there. 31:13.720 --> 31:19.720 Still people are still working on bringing it to the open source side. 31:20.720 --> 31:23.720 Hi. 31:23.720 --> 31:27.720 There was an interesting talk about IDX this morning. 31:27.720 --> 31:29.720 On K-CAD side. 31:29.720 --> 31:37.720 Do you know if FBTA is planning to do anything regarding IDX and collaboration with E-CAD? 31:37.720 --> 31:39.720 It's gone. 31:39.720 --> 31:40.720 No. 31:40.720 --> 31:48.720 Honestly, I haven't seen anything coming away regarding IDX in frecad so far. 31:49.720 --> 31:54.720 So it's not in our plans, but just a matter of someone coming to us with it. 31:54.720 --> 31:55.720 Basically. 32:09.720 --> 32:10.720 Hi. 32:10.720 --> 32:14.720 Is edgy interested in the energy aspect for the future? 32:14.720 --> 32:20.720 But the plans for this, are you thinking of energy plus integration and things like this? 32:20.720 --> 32:21.720 Yeah. 32:21.720 --> 32:23.720 That would be at the moment. 32:23.720 --> 32:28.720 Energy plus is the only viable solution that's fully open source. 32:28.720 --> 32:30.720 Energy plus is a program. 32:30.720 --> 32:32.720 It's an open source solution. 32:32.720 --> 32:36.720 And it's plugged into a constellation of small pieces of software 32:36.720 --> 32:40.720 who together do an energy element analysis of building. 32:41.720 --> 32:48.720 And as far as I know at the moment it's the only pipeline that can produce the final result of a, 32:48.720 --> 32:53.720 let's say, something you can use for a building permit or something like that. 32:53.720 --> 32:58.720 So that would be the probably at the moment the best part to go. 32:58.720 --> 33:05.720 I would say we have a lot of work to be done before being able to use one of those things. 33:05.720 --> 33:11.720 Our part in frequent would be to produce a model that is ready for energy analysis. 33:11.720 --> 33:18.720 And that means it's a bit different than a normal beam model where every little screw, 33:18.720 --> 33:21.720 every little thickness is is modeled. 33:21.720 --> 33:25.720 An energy analysis model is basically only faces. 33:25.720 --> 33:31.720 For example, over house and every face defines what's inside, what's outside, 33:31.720 --> 33:36.720 and what's the resistance to energy. 33:36.720 --> 33:45.720 And so we still have a lot of work to transform a beam full beam model with all the columns 33:45.720 --> 33:50.720 and the roof and the floor into such a simple analysis model. 33:50.720 --> 33:53.720 I would say that's the part we should do in frequent. 33:53.720 --> 33:55.720 That's where we should arrive in frequent. 33:55.720 --> 33:57.720 And then when we have that model, 33:57.720 --> 34:00.720 it's energy plus being something else that will be easy. 34:00.720 --> 34:07.720 We will have the model ready for plugging it into such a structure. 34:07.720 --> 34:09.720 Thank you. 34:21.720 --> 34:25.720 To expand a bit on the testing question. 34:25.720 --> 34:31.720 I see an understanding unit tests are small pieces of testing. 34:31.720 --> 34:35.720 The test individuals of some of the features, 34:35.720 --> 34:43.720 but what I would like to see are there any ideas on having database of complete projects, 34:43.720 --> 34:50.720 or you'll start out automatically the whole free card and then repeat it. 34:50.720 --> 34:52.720 Yes, definitely. 34:52.720 --> 35:00.720 Peter Hema, who is a free card developer, has a project that generates documentation 35:00.720 --> 35:09.720 that is all the sheets of building manual for the microcontroller that it's on the free card table there. 35:09.720 --> 35:14.720 And so all the documentation, step one, you take two screws, step two, 35:14.720 --> 35:17.720 you put the two screws in whole A and B. 35:17.720 --> 35:25.720 But I mean, what things we discussed that I would like to happen is to use that kind of stuff 35:25.720 --> 35:33.720 to test a whole workflow in frequent and to automate a kind of complete work in frequent. 35:33.720 --> 35:38.720 That's the kind of project that we could use to do that kind of stuff. 35:38.720 --> 35:42.720 And then you have a huge database of projects. 35:42.720 --> 35:46.720 And then you can run basically locally. 35:46.720 --> 35:52.720 And after an hour you get a complete test suite result for... 35:52.720 --> 35:54.720 Yes, that's cool. 35:54.720 --> 35:56.720 You can already do that with our unit tests. 35:56.720 --> 35:58.720 It tests basically, it tests the line tool. 35:58.720 --> 35:59.720 It tests the sketch tool. 35:59.720 --> 36:03.720 It tests the putting creating an extrusion, etc. 36:03.720 --> 36:05.720 And you can run them all at once. 36:05.720 --> 36:07.720 And it tests everything in frequent. 36:07.720 --> 36:11.720 It opens, frequently we will see frequent open on your screen and doing stuff, 36:11.720 --> 36:13.720 opening files and closing files. 36:13.720 --> 36:15.720 And it will test everything at the end. 36:15.720 --> 36:20.720 You have a progress bar and it passes or it tells you where it fails. 36:20.720 --> 36:23.720 But this is running every time we compile frequent. 36:23.720 --> 36:27.720 So normally no frequent gets out there. 36:27.720 --> 36:31.720 That didn't pass those things. 36:31.720 --> 36:34.720 All right, thank you, York. 36:34.720 --> 36:36.720 Thank you guys.