kicad-developers team mailing list archive

[Cirilo Bernardo <cirilo_bernardo@xxxxxxxxx>]

----- Original Message -----

> From: Dick Hollenbeck <dick@xxxxxxxxxxx>
> To: Carl Poirier <carl.poirier.2@xxxxxxxxx>
> Cc: KiCad Developers <kicad-developers@xxxxxxxxxxxxxxxxxxx>
> Sent: Friday, October 4, 2013 5:24 PM
> Subject: Re: [Kicad-developers] Github plugin.
> 
> On 10/01/2013 08:47 AM, Carl Poirier wrote:
>>  Hey I forgot to tell you yesterday that while moving the libs to GitHub, I 
> had to rename
>>  the "smd_crystal&oscillator" one since GitHub doesn't 
> allow the '&' character to be used.
>>  I called it "smd_crystal_and_oscillator", and thus it will fail 
> with any fp-lib-table
>>  based on the one I sent earlier, which was tailored to the converted local 
> files.
>> 
>> 
> 
> 
> Quick poll:
> 
> What do folks think of *footprints* named like this?
> 
> 
>    SOT23_Transistor_BC846_Handsoldering_RevA_03Aug2010
> 
> 
> Attached is a revised fp-lib-table for GITHUB.  The nicknames are shorter, no 
> revisions or
> dates in them.
> 
> 
> BTW, I much prefer something like this:
> 
> 
> SOT23_Transistor_BC846_Handsoldering_RevA_03Aug2010_while_I_was_wearing_my_blue_shirt_after_lunch_where_we_ate_pizza
> 
> 


That sounds like a good idea.  I'm all burned out for the day so I can't think if there would be any advantage to component_package_.... rather than package_component_...  On the other hand, so long as there's an established naming scheme it will be possible to use key searches etc. to help users filter and wade through huge libraries in the future. I have a feeling some other metadata would also be useful such as any notes on compliance to specific standards and so on; this helps keep file names short by keeping the fine details elsewhere.

- Cirilo