New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Add GUI #26
Comments
It's a great idea that i have also in mind. |
I thought a bit more about this and in the end haveing the GUI just out of the PCB editor is kind of limited. |
|
What I wanted to say is that a GUI that can just be used out of the PCB editor is not ideal because you may also want to use it from within the schematics editor. With "not a big deal" I meant that it is equaly easy to build a standalone GUI compared to an action plugin. I did a quick experiment yesterday but that was just a quick and dirty proof of concept so far: Here are some of my thoughts / how I did things for my test:
I'll keep you up to date on my experiments! |
I implemented a very basic version of this proposal, you can have a look at it here: https://github.com/Bouni/easyeda2kicad.py/tree/gui If this goes into the right direction for you I'll put in some more effort and prepare a PR |
Thanks for your details explanation, i get it.
Sure, i think the best solution should be to access the plugin in Eeschema and Pcbnew. But it seems that's tricky to create a plugin in Eeschema right ? |
Sure it's seems fine for me.
I'm too busy this week to work on the project, but will definitely work on it next week ! |
At the moment it's not possible to have eeschema plugins! That'll com down the road towards V7 but nobody knows when that's the case ... Good points you got there! |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
I keep working on this but progress is slow (wx sucks to be honest 🙈 ) |
Ok |
Tkinter and Qt come to my mind but I've never used one of them before. Maybe using a TUI is an option, like https://github.com/bczsalba/pytermgui And last but with the most work needed, a web API (maybe fastapi) and a Vue frontend that runs in a browser. Many options, all with their pros and cons. Creating a nice looking UI in wx is a pain in the rear but might be the easiest way to do it ... |
I agree |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
This issue was closed because it has been stalled for 14 days with no activity. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
This issue was closed because it has been stalled for 14 days with no activity. |
@Bouni, would it not be possible for your kicad-jlcpcb-tools plugin to show a "Fetch EasyEDA model" button next to a JLPCB component, and when pressed call |
@hattesen This might be possible but see it as a future goal and not a simple low hanging fruit type of thing. |
@Bouni maybe you are interested in this: Maybe you guys want to check it? I stepped away from doing it in wxwidgets directly in KiCAD because there is not much gain having it in there, but maintaining it is kind of a nightmare. https://github.com/markusdd/EasyEDA_to_KiCAD_Lib_UI I released a first windows build, more to follow. I have not used easyeda2kicad though but JLC2KiCad_lib. |
I love this plugin but it feels not really integrated. I think a GUI woud be absolutely awesome!
It could be super simple, maybe just a single window that shows up after the user clicks the action plugin button.
There you got the options (checkboxes, radios, whatever) and paths which could be saved in a YAML/TOMS/INI file beside the plugin itself.
And a textfield for the LCSC number plus a Go button to download the data.
Actually not that big of a deal to build and would make the plugin usable from within KiCAD.
The text was updated successfully, but these errors were encountered: