91–100 of 105 posts
Earlier quoted context omitted.
Why aren't there Linux builds? I'd love to try it out but this immediately makes it impossible for me.
There's a flatpak binary for it https://www.flathub.org/apps/details/org.horizon_eda.Horizon...
Author here, ask me anything.
Great. Here's one: When producing a placement file for a PCB, can component part numbers be exported ? Neither Cadence, nor KiCAD stores components in their PCB files, only footprints, so part numbers cannot be easily accessed.
Earlier quoted context omitted.
How is this different from LibrePCB and why you have not joined forces together?
I only got to know about LibrePCB at the end of 2016 after several months of development on Horizon EDA. While there are some similarities such as the use of UUIDs and strong link between schematic and netlist, there are major architectural differences such as Horizon EDA using raw OpenGL vs QTSceneGraph(?) and Gtkmm vs QT. As far as I can tell, the development models also differ significantly: The LibrePCB devs seem…
We also talked about ways to increase collaboration between the two tools. A few ways I could see is:
* Router: Extracting the KiCad router into a separate repository / library so it can be used and developed by the different projects.
* Gerber Compatible Stroke fonts: Would be nice to have one font specification and implementation to be used for PCBs. LibrePCB started the FontoBene (https://github.com/fontobene) project to do just this, but currently LibrePCB is the only user of it.
* Regular exchange of ideas and domain specific problems / challenges and solutions. This already happened a few times at c3 and FOSDEM.
The PCB EDA space really needs some competition. Kicad is really getting there, it "just" needs some UI improvements (Automation of the Schematic->Netlist->pcbnew flow would be nice) and also some of the big boy features like signal integrity and heat etc. Altium is probably the only clean PCB experience at the moment, and even that sits at 10% CPU on my machine with an empty schematic and no PCB open. The more esote…
> it "just" needs some UI improvements Yes unfortunately the develops are not receptive to improving this. They feel that any attempt to make it more intuitive or easy to use is dumbing it down. Disappointing.
Is there work being done on the project that you feel should be prioritized below certain UI changes?
Author here, ask me anything.
A few questions from an Altium user: 1. Does Horizon support an equivalent to the 'Variant Manager?' This is something that will allow variance of build outputs (different component populations, different schematic text, etc). 2. In the docs it seems to mention submitting parts to the default pool. If people submit parts to the pool are there style guides somewhere? (line widths, US vs EU resistor symbols, etc) 3. Lo…
No, but there's been some discussion on it: https://github.com/horizon-eda/horizon/pull/347#issuecomment...
> 2. In the docs it seems to mention submitting parts to the default pool. If people submit parts to the pool are there style guides somewhere?
There's https://github.com/horizon-eda/horizon-pool-convention, but that's still work in progress.
> 3. Is there a way to set paste mask expansion like is done in Altium?
Yes, you can set it globally in the board.
Earlier quoted context omitted.
Scroll wheel and middle mouse button, as commonly used in most software. Home button reframes the view.
In my commonly used software I click on damn things, little boxes appear on corners and I can just drag them in/out to decrease/increase the size. Or if 3D software I have 3 more lines to rotate/roll for each axis. That's my commonly used software.
Earlier quoted context omitted.
Absolutely! As long as those tools can communicate with each other à la unix pipes
Why limit with OS specific tools? Why not just communicate via markup files?
The PCB EDA space really needs some competition. Kicad is really getting there, it "just" needs some UI improvements (Automation of the Schematic->Netlist->pcbnew flow would be nice) and also some of the big boy features like signal integrity and heat etc. Altium is probably the only clean PCB experience at the moment, and even that sits at 10% CPU on my machine with an empty schematic and no PCB open. The more esote…
KiCad just drags stuff from very old days. The concept of having split tools for schematic and pcb just doesn’t cut it any more. Nowadays most companies have transitioned or are transitioning to do layout inhouse, because modern products are so integrated that the “old ways”, doing sch inhouse and sending it to a company for layout has become very cumbersome. IMO one of the key things for any new EDA package is makin…
but kicad at least has an approachable format. so I wrote some crappy tooling to at least generate symbol and layout from a single description. and I could theoretically write a front end and leverage things like Gerber generation.
I don't understand why we don't have vendor supplied footprints in a tool-neutral textual format yet. I know people have tried - who are the contenders?
The PCB EDA space really needs some competition. Kicad is really getting there, it "just" needs some UI improvements (Automation of the Schematic->Netlist->pcbnew flow would be nice) and also some of the big boy features like signal integrity and heat etc. Altium is probably the only clean PCB experience at the moment, and even that sits at 10% CPU on my machine with an empty schematic and no PCB open. The more esote…
A year and a half ago we abandoned using Cadence and Altium in favour of KiCAD. Extremely high cost of licensing was a reason, but not the only one. Our first steps with KiCAD were hard and tiresome, my engineers even tried to sabotage the work a couple of times. But now as we got used to KiCAD I'm pretty much happy with this decision. KiCAD's GUI needs rework, also its net naming convension is flowed (try to re-anno…
If they’ve improved it I might give it a chance
Earlier quoted context omitted.
As an absolute beginner learning how to design PCBs and simple circuits for hobby projects - I have to say while KiCAD is getting there, it really still has a learning-curve of a sheer cliff. The interface and workflow seem arbitrary and unnecessary complex for what should be a relatively straightforward process. I realize this tool is far more powerful than I'll ever need but it really does feel like I'm in way over…
>Electrical engineers are willing to put up with so much more it seems. In general, IMHO. EAGLE, a golden-standard proprietary EDA tool, while still being quite a bit ahead of KiCad on the UX front, features no fewer pitfalls and completely unintuitive controls.
In what way? I've never heard of anyone doing "serious" (like sense FPGA routing etc.) In eagle
