On 22 December 2016 at 14:01, Strontium <[email protected]> wrote: The issue with the keys isnt that they are customisable, its that they are > easy to type wrong/get inconsistent, you have to remember what keys you are > using, did you leave any out, etc, etc. > > In this situation, we could define a "default" set of standard keys, like > "MPN", etc. Users would be able to define their own sets, add or delete > from the "default" set, etc. Tool writers would invariably use the > defaults, unless there was a good reason not to. Its not proscriptive, > just suggestive. > > So, rather than a change to the schematic file, its a UI change and a > change to an existing config file, or a (my preference) new config file. > I am happy with this solution and would be willing to work towards a patch. Would a patch for this be accepted?
The only open implementation question would be how to handle multiple manufacturer+MPN fields. On 22 December 2016 at 19:31, Clemens Koller <[email protected]> wrote: > It should be easy for KiCad to browse through the libraries and designs to > grab all used key names to get a dicitionary of used keys. A quite useful > feature would then be to rename, map and merge the keys to create > your-very-own "standard". > Having your very own standard kind of defeats the purpose of a standard :). I do this to a degree with 1clickBOM <https://github.com/monostable/1clickBOM#field-matching> but there are *so many* possibilities and it only really works in one direction, i.e. where do you put the information when you want to put it back into the schematic? It just seems like a lot of trouble for no gain at all: we are all talking about the same thing, an MPN, let’s agree on a name and where to put it.
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
