Replies: 2 comments 2 replies
-
Hey @set-soft, this is a great idea and I thought about this last year. Unfortunately I'm not a good programmer and mostly I work in egui (rust lang) projects as maintainer or tester atm. Great would be, to have a native and web app (which is pretty complex but for the crossed platform kibot it could be a good option because people with different OS use kibot continuously). The question is if the app should just generate a Example: Should setting global variables like I think this GUI has a lot of benefits and could help none KiCad proffesional to setup the kibot and their kicad project pretty well! If you wish to collect some ideas for a UI, than I could create some diagrams of my workflow and explain my usage of kibot. From my side, we use Kibot in over 40 projects now but mostly I need to guide my coworkes with writing the yaml. Please let me know if someone like me could help at this point. Thank you for KiBot! Best regards from Germany 🇩🇪 |
Beta Was this translation helpful? Give feedback.
-
The web app is interesting, didn't thought about it.
Hmmm ... I think preflights are intended to do this kind of modifications. You can config KiBot, then run it and get changes consolidated to the schematic and or PCB.
I want to focus on what should be validated and how. But workflows could also help.
Did you try using parameters as used in the internal templates. I think we need more internal templates to cover the most common outputs.
I think you could take a look at the templates parameters, I now realize that the GUI should offer some mechanism to easily choose some templates.
😀 |
Beta Was this translation helpful? Give feedback.
-
I might be dedicating some time to this. I would like to know:
I think the value here could be in the fact that you won't need to remember the name of the options.
Beta Was this translation helpful? Give feedback.
All reactions