kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #10477
Re: Terminology footprint vs module
On 05/24/2013 03:49 PM, Dick Hollenbeck wrote:
I think in the future it would be nice if a module could hold tracks and vias, in addition
to one (or several) footprint(s).
So the answer to your disciples might be that a module is potentially a superset of a
footprint.
If and when that happens, we will need both terms, so there is insufficient justification
and motivation to eliminate one term now IMO.
Uhh .. I'm not for eliminating any term - just for eliminating using two terms to mean one thing.
So if the footprint field in eeschema is naming a module - why not call it 'module'?
If the module starts pointing to a footprint later - reintroduce the term on the PCBnew side (
replacing something like the xxx.emp file?)
Works both way - if a module becomes more of a super-set tomorrow or not.
,.,.,.,.
On 05/24/2013 04:29 PM, NHays Terrace wrote:
> Is it appropriate to create a graphics& text only module?
I've done that - it works for putting Logos etc.. I think of it as a pad-less footprint..
--------------------------------------------------------------------------------
Karl Schmidt EMail Karl@xxxxxxxxxxxx
Transtronics, Inc. WEB http://secure.transtronics.com
3209 West 9th Street Ph (785) 841-3089
Lawrence, KS 66049 FAX (785) 841-0434
Truth is mighty and will prevail.
There is nothing wrong with this,
except that it ain't so.
--Mark Twain
--------------------------------------------------------------------------------
References