← Back to team overview

kicad-developers team mailing list archive

Re: Github plugin.

 

Hi guys,

My replies to some of your comments are below.


> That table currently gets set only on entering the dialog.  I will look at
> this and see if
> I can trigger another env-var fill after editing any lib path (uri).



The env-var table should be read only.  I am working on that today and will
> change it to
> such.  This env-var table is just a reminder, not a tuning agent.



It will show any environment variable referenced in a LIBPATH, if that
> env-var is in the
> libpath at time of invoking the dialog (for now).  Only those environment
> variables
> referenced in a libpath are shown.


Actually it was me not knowing the difference between shell and environment
variables. I got it to work now, although the changes in the env are only
reflected once I restart pcbnew, and not when I close and open again the
library dialog.

The last step is to push to GITHUB.  I don't see a reason to wait, since
> the footprints can live in several places at once.  The real question is
> when do we shut down the BZR library repo, not when do we push to github. For
> now, you could make each *.pretty directory its own github repo, local to
> your work environment. Each should be a separate repo I think so that
> they end up being separate repos on github. [...] Once you do that, you
> can then push each repo to a place on github, hopefully under a common
> github user, and publish that base user location on this list.


No problems getting GITHUB_PLUGIN to build. I've not connected it to a
> github repository as I run out of time last night to generate a library.
> I'll have a look at it tonight and see how things go.


I can work on pushing the libs to github today. However, can you please
explain to me what you intend by a "common github user"?

We will soon need an official github librarian for the official kicad
> footprints.  This
> will require somebody to volunteer for that responsibility.


Actually I might be interested in that, but I'd like to know more about the
involved tasks. Since KiCad is the first project I contribute, you will
guess that I've never been an official maintainer.

Finally, I have included the script to generate the pretty libs as well as
the column swap in the attached patch. As for the library table that gets
saved automatically in ~, what do we want to do with that? I have also
attached it.

Carl

Attachment: lib_convert_batch.patch
Description: Binary data

Attachment: fp-lib-table
Description: Binary data


Follow ups

References