| delorie.com/archives/browse.cgi | search |
On Tue, Aug 25, 2015 at 7:49 PM, DJ Delorie <dj AT delorie DOT com> wrote: > > In both cases there's a many-to-one relationship; one schematic can be > used for many purposes, and one pcb is made of many schematics. I almost want to write a netlister that lets you move files and the functions that process them around in a schematic so that you have a graphical view of workflow. gschem -> schematic file -> gnetlist -> makefile > So gschem would have to have many buttons, one for each purpose the > schematic is used for, but pcb would only need one - to collect the > things it needs. PCB's File->Import does this; it knows how to use a > list of schematic pages or call out to a Makefile to get what *it* > needs. A "getting started" button on gschem would need to assume that > the one schematic is sufficient for one pcb, or figure out how to ask > the user what other schematics are needed. Also, not everyone starts > a pcb with the import - I prefer to lay out the board's boundaries and > physical size first, *then* import. > > BOMs are trickier, because you need to know the set of schematics but > you also need to know the build-out of the board, i.e. which > configuration of parts is populated. I typically use a script to > generate a BOM from schematics on a per-pcb basis, using attributes > from the schematic, but I can't see that working as a button in either > gschem or pcb. Also, if your sch->pcb tool modifies any of the parts, > the BOM generator would need to know about that too. -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |