I am looking at trying to even import a premade Teensy 4.1 footprint. I find it rare that a user interface is so opaque that I cannot even imagine to understand what the creator is trying to do, and that’s where I am.
I’ve used Kicad for at least 120 hours, now. I have found only a minor bug or two. It needs a hot-key for constrain (which would speed Kicad’s use). Except for the part and footprint Library, I am pretty happy with Kicad. In fact, I have shown it to several electronic and SI engineers in Silicon Valley, and have said good things about it : ) (Thank you)
I strongly suspect that Kicad’s code is quite sophisticated, but therefore complicated, which requires a lot of attention to detail. The problem likely comes with a myopic (nearsighted) attention to detail: it becomes difficult to see the big picture, as if the functionality was written from the back-end toward the front. I think that the programmers pulled off a great feat that their code has reached the top, but it appears a GUI designer should have met them just before that.
Let’s see…
1.) The Add Library and New Library thing should go away. Pick a metaphor and roll with it. I should think that most people have never encountered a UI decision like that. If you are adding to an existing opened library, please change legend on the menu.
2.) I tried both creating and adding a library for both project and global. A matrix of four tries to see what happens. It’s not easy to notice something as major as a custom part folder in the Save Footprint menu. For this, I felt something I have almost never felt for a user interface–even from the deepest bowels of the engineering software ghetto–frustration.
What I wanted: See that I was having difficulty, I wanted to soldier through the import footprint (into my project), and offer meaningful suggestions on how to make the process smoother.
What happened. I still may not have have my footprint in.
[Oddly, I had lesser of a problem with a Kicad version from a few years ago.]
I imported a footprint, and tried to save it, but I must save it–and yet I it’s not easy to notice the library names I have created, nor do I have idea where the main Kicad library is located. I see the library folder with my project folder, but what of it? Is it open? Okay it’s there, now what?
As far as the main Kicad library: if I want to move it to say, dropbox, well, where is it? In this case the metaphor of a Word processor spell check-file chooser, which shows the location, would be great. If it’s in xxxx folder, well then show me it is. This is a good way of handling paths, though Libre they have used the Window ap-data folders. (Please don’t get tripped up thinking that I have only used word-processors or anything like that.)
3.) If I add any footprint to a stock Kicad installation, surely I want those flagged and searchable, so, I know what to bring to a new machine/installation.
4.) Generally, and it might already be this way, but Kicad’s stock libraries should be unmodifiable/immutable, so an new, inept user like myself won’t mess things up.
5.) It would seem that the per-project libraries should be saved in the project folder, but it should be easy to copy/import all the parts from the user’s custom folder for use in a project, perhaps something like this:
Note: “Pretty” means very little to user as an extension. I fear for what came before it, though.
6.) (Edit) I created a IRL640A MOSFET symbol, which I want to share. It has the correct diode and pinout. It’s in the schematic, working, but from the Symbol Editor I cannot search for it, to export it, but it doesn’t show up. Though, for some reason, if I click on it in the schematic and edit it, I can export it.
~
Going further, an Cd-DB style thing so that users can upload, download, and rate parts–would have the people at Eagle and those who make online PCB creation tools–waking up in nightsweats. Please, make it easy to share symbols and footprints. It would be swell, if a complete package was 7zip’ed, With symbol, model, nomenclature, kit and caboodle. Is that a .pretty file. I don’t know.
Thank you for working on Kicad, and also reading this far.