At my workplace, we use this workflow as well. Each real "part" is a symbol as its base, with BOM info in the symbol properties, with a specific footprint for each part. Out of the four EE's doing schematic/layout here, we never open CvPCB.
-- Justin Partain On Thu, Feb 2, 2017 at 10:28 AM, Clemens Koller <c...@embeon.de> wrote: > Hello, Chris! > > Eeschema -> Schematic editor > > Pcbnew -> Layout editor > > Cvpcb -> move it to Library editor or manager > > BTW: Assignment of a footprints seems to me completely odd at this level. > > When I create a part it consist of a partname, schematic symbol, an > assigned footprint, a 3d-model, and some attributes all in > one place. Then I grab that part by its partname (like the handle of a > suitcase) and use it in the schematics. From there it gets > forwarded to the layout, bill-of-materials and assembly data and > optionally to an 3d-renderer without any additional tweaking. > > A part to buy, i.e. named "LTC6362CMS8" comes already with all the > information to be placed in the suitcase - it has exactly one type of > footprint (here MSOP-8, JEDEC MO-187-AA). I don't see any reason to assign > different footprints to parts, because they usually have only one. > > It's a different story if there will be some solder yield tweaking to > automagically replace/update *all* footprints of a design by using a > different process library. (i.e. use RoundRect shapes vs. Rectangular > shapes to improve tombstoning or solderpaste release.) > Here, we are thinking to generate footprints dynamically depending on > soldering process parameters - but an MSOP-8 will still be an MSOP-8. > > Pl Editor -> Template editor (we might want to edit other stuff as well > such as board outlines for PCIe and similar things) > > Bitmap2Component -> Remove as independent app, make "Import image" in > libedit and modedit (dito.) > > > Regards, > > Clemens > > > On 2017-02-02 14:56, Chris Pavlina wrote: > > I admit I'm getting self-indulgent here, this request is definitely a > > bit "what Chris would do if made Dictator of KiCad", but... just testing > > the waters here: > > > > What do people think about, for either the 5.0 or 6.0 release, ditching > > the old application names, in favor of everything being one tool under > > the "KiCad" roof: > > > > Eeschema -> Schematic editor > > Pcbnew -> PCB editor, or Layout editor, or Board editor > > Cvpcb -> "Assign Footprints" > > Pl Editor -> Title block editor > > Bitmap2Component -> Remove as independent app, make "Import image" in > > libedit and modedit > > > > I know this one is going to be controversial, but I don't really see the > > point of these old names. They're... weird. Cvpcb - what does that even > > mean? :P > > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
