Re: [Kicad-developers] [RFC] Standard field for manufacturer part number in schematic symbols

I see a lot of confusion here between what is a schematic part. usually a circuit is designed around a specific part, i.e. a Texas NE555 in SO8 package. This part has a very specific set of parameters, and a similar part from another manufacturer, i.e. Fairchild might have some parameters that mak

Re: [Kicad-developers] [RFC] Standard field for manufacturer part number in schematic symbols

Hello, Kaspar! I am not happy at all with embedding information in pre-defined (hardcoded) fields/attributes/labels. Simply because I think there is simply no standard way to do that. Here, we keep all non-mandatory or volatile information of the components outside of the schematics in a separ

[Kicad-developers] [RFC] Standard field for manufacturer part number in schematic symbols

Hi all, there has been a lot of discussion lately about a standard manufacturer part number (MPN) field in schematic symbols in the user forum and on the standard library GitHub issues

Re: [Kicad-developers] Release 4.0.5 tagged.

Yes, thank you all. We can now call the release done. 2016-12-20 20:52 GMT+01:00 Adam Wolf : > The OS X build with PDF docs works great. It's uploaded to the right place, > and I notified Nick. > > Adam Wolf > > On Mon, Dec 19, 2016 at 9:46 PM, Adam Wolf > wrote: >> >> Sorry for the email bombar

Re: [Kicad-developers] Release 4.0.5 tagged.

The OS X build with PDF docs works great. It's uploaded to the right place, and I notified Nick. Adam Wolf On Mon, Dec 19, 2016 at 9:46 PM, Adam Wolf wrote: > Sorry for the email bombardment. > > If I remove the html help docs, it falls back to the PDF help docs, which > seem to work great (an

Re: [Kicad-developers] [PATCH] eeschema new tool/feature: Component spreadsheet tool

Le 08/11/2016 à 01:29, Dino Ghilardi a écrit : > Hello everyone, > > Thanks for the comments on this tool and the video. > > Attached there is the first patch for the 'component spreadsheet' tool > (probably the temporary name > for this "table based design entry", as points out Clemens). > > O