 Right, so I'm going to talk about a bill of materials editor that I'm working on for Kitspace.org. So Kitspace.org is a project sharing platform where you pretty much at this stage, you put stuff in a Git repository somewhere and send me a link or send me a full request on GitHub to add your project. And the idea is to have this repository of easily replicable designs. So on a Kitspace page, you have a way to see what the PCB would look like and you can download the Gerber files or it's got links here to go to Isla or PCBway to have it made. And I spend a lot of time on these tools to automate the parts ordering process. So there's buttons on there which uses a browser extension called the one-click bill of materials browser extension to automatically add components to retailer shipping cards. So the problem with this is obviously it's quite hard for people to properly document their bill of materials and actually even a lot of the projects on GitHub on Kitspace already, they don't have bills of materials that are purchasable because it hasn't been fully documented. So it's quite a, I guess, a frustrating process for people to go through this. So I've been working on this editor tool right now. It's a standalone kind of web application. The idea is to integrate this into Kitspace so that when you press edit a project, edit the bill of materials on Kitspace, it would be something similar to this. So I'm just going to show you like the workflow in this. This looks out of date. There we go. This is the new one. So the idea really here is you can open your existing bill of materials and you can even import a KiteCat PCB already. So we're going to try that. So this is the PCB from the ruler. Currently this means it's thinking. You can import there and it grabs, tries to grab the descriptions of your project. You can then look at this and maybe reduce this down a bit. Really, this is a 1206 1K resistor and then it's going to understand that actually. So then you can go to Digikey and see whether you want to buy that one. You can select it. You can select specific parts here and you can even, even for these, when it's, when it's, basically when it's, when this is green, it's pretty sure that it knows that you want this part. So I've been working on doing this auto-filling so it will select all these parts for you there. This magic wand means it's like this is already a part that you've selected. So it's really sure that you, you want this part number in here. So what's the time I'm doing on time? Five minutes ago, I should have stopped. Five minutes, five minutes to go. I can, well, I can go back to the demo. I'm just going to finish off like, because this is a software, I'll have a conference talk a bit about the, the actual, the, how this is made. So these are the kind of the features. Currently you can import the bomb and you can import the KiCAD PCB. You can quickly select parts and then you can download a CSV file, which you can then use to add a kid space project or, you know, you can keep it for yourself. You, the plan with this obviously is to integrate it into kid space and have more CAD imports for all the different CAD files and kind of grab the, the bill of materials information from there and help you make a proper bill of materials out of that. We want really better price information and like price summaries and being able to reduce the, the bill of materials by price to optimize for price or to optimize for what retailers you prefer or anything like that. We need more accurate price information to do that. I've almost finished this part to then go from here from the, have a button here to kind of reduce the bomb bill of materials to your preferred retailer and then use the one click bill of materials, Bauer's extension to, to buy the parts. So you can easily from your bill of materials making process go to your shipping cart. So, nope. So the architecture is fairly boring. I mean, I'm, I'm kind of a language nerd and for this, for all this kid space stuff, I just, I kind of, so far I stick to JavaScript and like modern established working ways in JavaScript. So it's kind of has the most, most of the, a lot of stuff is on the client side and this application is kind of almost like a standalone. This is like, it's statically, it's static hosting and then the server side is just currently a single application that just kind of hooks into other APIs and gets the information. It used to do some scraping as well. I've just stopped that, but I could again also use scraping techniques to get the information into there and the reason it's not just using Octopart API because there's some improvements on the stock information, the price information that we can get from other places. Octopart is a great API, but it's not perfect. So client side, like I said, really boring stack, kind of modern using React. Using semantic UI, which is like the user interface. It allows me to not worry so much about how things look and I'm fairly happy with this, the kind of default styling for semantic UI. So I don't spend a whole lot of time on how that looks. So the server side, more JavaScript, Node.js and the reason for this, that I keep using JavaScript is so that I can develop libraries that I can either use on the front end or on the server side and I can pull them in and use them on both sides. One of these libraries is the Electrogrammer, which I've mentioned in the talk last year at Fozdem, which is a... I don't think we have time for this API demo. Electrogrammer is a JavaScript library to parse electronic components descriptions and this is really what makes this tool more usable than just straight up the standard Octopart search or IAPI access. How am I doing on time? One minute. So I've just started trying to finance this project a bit more because I spend a lot of time on this. So I've just opened an open collective, so if you start using these tools and you find them useful, please consider supporting these projects. There's other people, obviously, my cousins, the whole thing on Kidspace with how the Gerber, the Gerber preview of your board, that was an amazing project called PCB Stackup by my cousins who has done an amazing job with it. David Curvin has helped me on Electrogrammer and I'm hoping we're going to get more contributors. So I think this kind of collective way of receiving donations would work for this. Maybe we have time for one question. If you... Sorry, I didn't... I wouldn't say we're duplicating a standard. We're using the existing standards and the existing language that engineers use, but we're making it like a simple interface for understanding that language. I guess I didn't understand your question fully. Yeah. Um... I think there is no such standard. Well, I guess the answer to the question is there is like the JetEx standards and the other standards for how to describe components and we're trying to use all of that. We're trying to use all of that so that you can just write that name and then the parser understands what you mean. Okay.