kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxxxx>]

On 10/30/2013 12:44 PM, Dick Hollenbeck wrote:
> On 10/30/2013 11:34 AM, Carl Poirier wrote:
>> I'll do it.
>>
>> Where does the number 25 come from? If it's just a number off the top of your head, I'll
>> do some resolution tests and see what looks good for say a minimum of 1280px width.
>> (Netbooks will excuse me)
> 
> IMO if a KiCad user is not using a dual monitor for design, then his employer is
> under-valuing his time.  Employer is customer or boss or self.  This opinion extends well
> beyond netbooks being inadequate.
> 
> 
> 25 is arbitrary (arbitrarily short).
> 
> 
> You need commit rights to library repo or already have them?  I will implement the CMake
> uninstall feature for the libraries, so the old ones can be yanked in our linux script
> before installing the new ones.  Or by anyone else using cmake for installation.
> 
> Fortunately footprint names are not changing, and footprints which are already in BOARDs
> are obviously not affected.  Schematic part libraries are not affected, 3D libraries are
> not affected.  Only footprint library names, and for a user using fp_lib_table support, he
> will be given your shiny fp-lib-table to ease the transition.
> 
> I don't know how to make improvements without change.
> 
> Any objections?

No objections from me.  I've already commented on this so I'm all for
it.  The folks that devised this naming convention may disagree.

Wayne

> 
> Dick
> 
> 
> 
> 
> 
> 
> 
>>
>>
>> On Wed, Oct 30, 2013 at 11:43 AM, Lorenzo Marcantonio <l.marcantonio@xxxxxxxxxxxx
>> <mailto:l.marcantonio@xxxxxxxxxxxx>> wrote:
>>
>>     On Wed, Oct 30, 2013 at 10:31:05AM -0500, Dick Hollenbeck wrote:
>>     > a) *Nicknames*: revise the template/fp-lib-table file wrt nicknames:
>>     >   i) no longer than 25 characters
>>     >   ii) adopt a consistent choice of capitalization
>>
>>     I think that's a good idea (altough it's more for the library people)...
>>     it's one little ugliness in the eeschema field, too. However I don't
>>     think that 25 should be an hard enforced limit, a guideline should be
>>     enough.
>>
>>     > b) shorten the name of *Library Path* entries, this means renaming most footprint
>>     > libraries in the bzr repo to remove any reference to date or revision and to remove any
>>     > inclusion of part names.
>>
>>     Same as above :D
>>
>>     > c) add the previously existing references to part names which were in the library names,
>>     > into the "Description" column of the fp-lib-table if the author so desires.
>>
>>     Also: do we really need so many fine-grained libraries, especially with the
>>     pretty format?
>>
>>     --
>>     Lorenzo Marcantonio
>>     Logos Srl
>>
>>     _______________________________________________
>>     Mailing list: https://launchpad.net/~kicad-developers
>>     Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>>     <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>>     Unsubscribe : https://launchpad.net/~kicad-developers
>>     More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>>
>> _______________________________________________
>> 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
>>
> 
> 
> _______________________________________________
> 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
>