kicad-developers team mailing list archive

[Dick Hollenbeck <dick@xxxxxxxxxxx>]

On Oct 4, 2013 12:08 PM, "Carl Poirier" <carl.poirier.2@xxxxxxxxx> wrote:
>
> I am also in favor of keeping simpler library names. The latest dialog
works well on my side, pasting the table from the README.md as well. Great
work there.
>
> I'll try in the next few days to get a README.md generated for each
pretty library.
>
> As for copying the whole table at once instead of going into each
repository, would having an empty repository containing only a README.md be
a good idea?
>

For the 'official' libraries you converted, I committed
template/fp-lib-table.for-github. which you can help maintain.

I added no cmake install support for it yet.  But its in the source repo so
it won't get lost on mailing list.

I doubt if all our official libraries warrant the term 'official'.  Some
seem highly personal.  Grouping and naming seem chaotic.

I don't see leadership in this work, sorry.

Opportunity for someone I think.



>
> On Fri, Oct 4, 2013 at 12:06 PM, Dick Hollenbeck <dick@xxxxxxxxxxx> wrote:
>>
>>
>> >> Short term our best options are to encourage preparation of a
publishing guideline.  That
>> >> document would talk about what constitutes a good library,
>> >> and how to prepare the
>> >> README.md file, and maybe even offer a wxPython script to prepare it
automatically.
>>
>> See
>>
>>    https://github.com/liftoff-sr/pretty_footprints
>>
>> for a quick initial attempt I made at manual preparation this morning.
 It allows:
>>
>> 1) quick copying and pasting of (fp_lib_table) element from HTML view at
bottom of page
>> into a blank row of DIALOG_FP_LIB_TABLE.
>>
>> 2) has hyperlinks to every *raw* format pretty file, (which when someone
adds (module)
>> s-expr clipboard pasting support to module editor, could be copied and
pasted from
>> webbrowser into module editor.)  This offers yet another way just to
grab one footprint
>> without bringing in the whole library as in 1) above.
>>
>>
>>
>