kicad-developers team mailing list archive

[Carl Poirier <carl.poirier.2@xxxxxxxxx>]

Sounds good to me. I'll look into adding some descriptions later on.
Anyway, it will not be a disruptive change...


On Tue, Nov 19, 2013 at 12:55 PM, Dick Hollenbeck <dick@xxxxxxxxxxx> wrote:

>
> Fantastic Carl!
>
>
> > fp-lib-table is attached. I also just committed minor corrections.
> Somehow a "bzr move
> > --auto" didn't work and I had to do it manually.
> >
> > As a general rule of thumb, the naming goes in this order:
> >
> > 1. Part type (resistor, cap, etc), must be in plural form
> > 2. Package type (SOIC, SMD, etc)
> > 3. Manufacturer
> > 4. Part number
> >
> > Naming uses underscores for spaces and the first letter of words is
> capitalized. As for
> > acronyms, all letters are capitalized. Finally, manufacturer name might
> also be
> > capitalized, depending on how it's written usually.
> >
> > Carl
>
>
> Thanks for establishing these guidelines.
>
> Thanks very very much.
>
> I committed fp-lib-table, but with a temporary filler Description of
>
>
>   "They way you like them."
>
>
> This is intended to suggest that if a user does not like them, they should
> submit patch,
> if even the patch is simply a better Description.  (A blank Description
> will not qualify.)
>
> I fixed a bug editing the Description field, change detection was missing.
>
> Imagine how much easier it is to simply move *.kicad_mod files from one
> *.pretty directory
> to another.  Or to take a footprint "export" file and simply copy it into
> a *.pretty dir
> to add it to your library.
>
> Or when a patch to a footprint is simply a patch to a *.kicad_mod file
> held on github in a
> *.pretty style github repo.  And the repo can be either installed locally
> or accessed
> read-only using GITHUB_PLUGIN.
>
>
> Those capabilities exist now.
>
> The fp-lib-table stuff is still not our default build, except for those
> using the
> kicad-install.sh script.   I don't think it is time quite yet to make it
> such, there are a
> couple things outstanding and more testing time is needed.  But we are
> getting close.
>
>
> Dick
>
>
>
> >
> >
> > On Tue, Nov 19, 2013 at 10:40 AM, Carl Poirier <carl.poirier.2@xxxxxxxxx
> > <mailto:carl.poirier.2@xxxxxxxxx>> wrote:
> >
> >     I have just committed the work.
> >
> >     FYI, I merged two libraries IIRC, something like "smd_resistors" and
> >     "Resistor_SMD_RevA" and another one.
> >
> >     I was about to send the fp-lib-table, but I'll double-check it using
> the hint you just
> >     gave me. BRB
> >
> >     Carl
> >
> >
> >
> >     On Mon, Nov 18, 2013 at 11:13 PM, Dick Hollenbeck <dick@xxxxxxxxxxx
> >     <mailto:dick@xxxxxxxxxxx>> wrote:
> >
> >
> >         Great, that news made my day.
> >
> >         I added the "Description" column to the module editor's "Current
> Library" picker
> >         dialog in
> >         the last day or so.
> >
> >         If that column makes sense also somewhere else, let me know.
>  Its probable I've missed
> >         another dialog.
> >
> >         And I wrestled with wx 2.8 most of what was an exasperating day,
> but eventually
> >         discovered
> >         how to make a darn wx 2.8 wxListCtrl come up showing its columns
> in full grandeur.
> >         Obviously this is a wx 2.8 bug workaround.
> >
> >         The Description field will assist new users in picking a
> library, and was originally
> >         initiated by an enhancement request months ago.
> >
> >
> >         Dick
> >
> >
> >
> >         > Actually it's all finished but one library. I sent an email to
> the
> >         lib-committers mailing
> >         > list for some more info on the "libcms" library, and am
> waiting for a reply.
> >         Here's the email:
> >         >
> >         >     Hi people,
> >         >
> >         >     As discussed in previous topics, I'm going through a
> rename of most
> >         libraries to have
> >         >     some consistency and also a more beautiful library table.
> >         >
> >         >     Looking at the library named "libcms", I can't really see
> what it is
> >         exactly, as I see
> >         >     no relation between its parts. Furthermore, its name says
> nothing to me. So my
> >         >     question is, what is this library?
> >         >
> >         >     Thanks,
> >         >
> >         >     Carl
> >         >
> >         >
> >         >
> >         > BTW, thanks Brian for the work flow explanation. It makes
> sense to me now.
> >         >
> >         > Carl
> >         >
> >         >
> >         >
> >         > On Mon, Nov 18, 2013 at 5:39 PM, Dick Hollenbeck <
> dick@xxxxxxxxxxx
> >         <mailto:dick@xxxxxxxxxxx>
> >         > <mailto:dick@xxxxxxxxxxx <mailto:dick@xxxxxxxxxxx>>> wrote:
> >         >
> >         >     >     >
> >         >     >     >     There is still no GITHUB_PLUGIN support for
> OSX.
> >         >     >     >
> >         >     >     >     Summary:
> >         >     >     >
> >         >     >     >     a) someone needs to create the github project.
> >         >     >     >
> >         >     >     >     b) someone needs to build GITHUB_PLUGIN on OSX.
> >         >     >     >
> >         >     >     >     Just talking and making suggestions is a far
> cry from that.
> >         >     >     >
> >         >     >     >     Carl at least stepped up.
> >         >
> >         >
> >         >     Thanks again for your help Carl.
> >         >
> >         >
> >         >     It will assist a number of folks in using the new stuff
> when people can see
> >         the whole
> >         >     table on screen:
> >         >
> >         >
> >         >
> http://groups.yahoo.com/neo/groups/kicad-users/conversations/topics/16501
> >         >
> >         >
> >         >     Please let us know if you will not be able to finish this
> in the next day or so.
> >         >
> >         >     Someone can spend 15 minutes and finish it up for you if
> its going to take
> >         much longer
> >         >     than that.
> >         >
> >         >     Dick
> >         >
> >         >
> >
> >
> >
>
>