GUI interface to create/edit KiBot configurations

[set-soft]

I might be dedicating some time to this. I would like to know:

• What people thinks about it?
• Any important detail that must be implemented in the GUI?
• Can you collaborate in the implementation? (I'm don't know much about wxWidgets)
• Do you want to donate to the project to accelerate this? (Want to be an sponsor?)
• etc.

I think the value here could be in the fact that you won't need to remember the name of the options.

[N0cynym]

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 .kiplot.yaml or could at least manipulate .kicad_sch and .kicad_pcb files!?

Example:

Should setting global variables like pcb_finish get just be printed into the .kiplot.yaml or could also be written to the PCB file!?

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.
I can understand a lot of very proffesional CAD designers that they love the result from kibot but won't struggle with writing a over 500 lines config file for it "from scratch"...
So I created templates for me which I can copy and paste and where I just replace placeholder variables to easily implement and fit kibot in a new project.

Please let me know if someone like me could help at this point.

Thank you for KiBot!

Best regards from Germany 🇩🇪

[set-soft]

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 web app is interesting, didn't thought about it.
But you don't have to worry about cross platform issues. I plan to try using wxWidgets, used by KiCad, so any GUI stuff will run in the same OSs where KiCad runs.

The question is if the app should just generate a .kiplot.yaml or could at least manipulate .kicad_sch and .kicad_pcb files!?

Example:

Should setting global variables like pcb_finish get just be printed into the .kiplot.yaml or could also be written to the PCB file!?

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 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.

I want to focus on what should be validated and how. But workflows could also help.

From my side, we use Kibot in over 40 projects now but mostly I need to guide my coworkes with writing the yaml. I can understand a lot of very proffesional CAD designers that they love the result from kibot but won't struggle with writing a over 500 lines config file for it "from scratch"... So I created templates for me which I can copy and paste and where I just replace placeholder variables to easily implement and fit kibot in a new project.

Did you try using parameters as used in the internal templates. I think we need more internal templates to cover the most common outputs.

Please let me know if someone like me could help at this point.

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.

Thank you for KiBot!

Best regards from Germany 🇩🇪

😀

[N0cynym]

Great to hear that you plan it to be cross platform.

You're right at this point I just forgot that this happens local. I use kibot in GitLab pipelines so preflights effect the file while the job and artifact lifetime but never change in my case the origin so I forgot that kibot still does this 😅

I think some diagrams of different workflows could help making the UI perfectly fit for each use case.

This is my GitLab workflow which I did specify:

At the moment I don't use the full feature set from kibot because I did not test or understand everything (so I use linux tools to do things like replace placeholders, zip or unite files...). But since you moved the documentation from the huge readme to the great docs page I do faster understand the features of kibot.

I hope to offer some templates as well.
Do you have any wishes how we (kibot useres) should provide kibot configuration templates?

Also do you need some easy graphics which could help beginners to understand kibot?
Like this:

I do create this graphics in draw.io so I could provide a project file if needed...

[set-soft]

Do you have any wishes how we (kibot useres) should provide kibot configuration templates?

Not really. I think that users could try to add a few parameters, like the internal templates provide. Then create common cases with unique names. As an example: the 3DRender template accepts _KIBOT_3D_VIEW, _KIBOT_ROT_X, _KIBOT_ROT_Y and _KIBOT_ROT_Z parameters. So you can easily create different views. But we have 3DRender_bottom, 3DRender_bottom_straight, 3DRender_top and 3DRender_top_straight, which are common uses. These common cases are implemented using 3DRender. So users can include 3DRender_top and get a nice top view without specifying a single parameter.

Also do you need some easy graphics which could help beginners to understand kibot?

I think that what we need are small how-tos. Things like: an example of how to solve X or Y problem.

Like in this repo: https://github.com/INTI-CMNB/kibot-examples-1 which renders to this https://inti-cmnb.github.io/kibot-examples-1/value_split/

I know this is an elaborated example, but simple examples could also help.