kicad-developers team mailing list archive

[Benoît Roehr <benoit.roehr.ec@xxxxxxxxx>]

Le 08/10/2014 19:40, Andy Peters a écrit :
> On Oct 8, 2014, at 5:08 AM, Mark Roszko <mark.roszko@xxxxxxxxx> wrote:
> > > I use footprint myself.  Though footprint seems to imply what a PCB
> > > must have in order to accommodate a part, eg, pads, silk.  Are the 3d
> > > models part of this?  If they are, then footprint might not be the
> > > best term.
> > > I agree with this. What you want to rename "Footprint" is more or less a container unifying different PCB objects (pads, lines, 3d model...), but may not be a footprint (logos, mounting holes, screws...)
> > Personally I think "Components" may be an even better word than
> > "modules" or "footprints" but suggesting that may have been even more
> > radical and conflicting agaisn't the next point
> My two cents, based on the terminology used by every employer for whom I've worked:
>
> a) A footprint is what defines how a part gets attached to a PCB. It includes the pad/holes for lead attach, as well as silkscreen for refdes and outline, and the other assembly layers such as soldermask, solder paste and glue dots. "Land patterns" really only describe the lead attach, and not the other stuff.
>
> I think Pads calls this a "decal." The only context I've seen the term "module" refer to a PCB footprint is in Kicad.
>
> "Footprint" is the term used by most of us here in the colonies.
Yes, i couldn't agree more :D
> b) A symbol is what defines a part for a schematic.
Well, seeing it from a productivity point of view, I prefer the term 
Component for the schematic. You are indeed using a symbol in eeschema 
but it represents a component.
> c) A component is the marriage of the footprint and the symbol, and possibly a 3D model, a SPICE model, a VHDL entity or Verilog module, and so forth. This is the Altium nomenclature.
Yes, except in all the libraries, every item in them are called 
component. Why ? Well I think they use the same library browser for all 
the library types, and Component is the default string in the list header.
> d) A module is a completed assembly or subassembly which is installed as one unit on a PCBA. The various DC-DC converters you can buy from TI and Linear Tech are modules.
>
> So my vote, if there's a move to change Kicad terminology, is to replace the term "module" with "footprint."
In my opinion, once the footprint represents a component, it should be 
called Component.

What I propose (if I can, I have not contributed that much for the 
moment) is to change almost nothingto how KiCad names stuffs already.

Here is my dream:

- In the Schematic Library editor, the symbol is the symbol you are 
drawing, but will be embeded in the component root with one or more 
footprint.
    Designator: Q?
    Value: 2N7002
    Footprint: SOT-23 / TO220 / MoreFootprints
    Datasheets: http://manufacturer-of-mosfet/2n7002.pdf

- In the Schematic editor, every symbols represent a Component which 
will be physically present on the board: for exemple:
    Designator: Q1
    Value: 2N7002
    Footprint: SOT-23< footprint selected for this project
    Datasheet: http://manufacturer-of-mosfet#1/2n7002_SOT.pdf

- In the footprint editor, you edit footprint, used by the components
- In the PCB editor, you deal with components having footprints, or free 
footprints representing other components.

From what I see in KiCad, all these stuff have already be done except 
for the multiple footprint selection and/or footprint direct linking (I 
haven't digged enough to use the 'filter'). The only occurences of 
Module I can see atm is in the PCBEditor and they should be replaced by 
Footprint or Component depending on the context.

See you :D
> -a
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp