Re: [Kicad-developers] Standard symbol field names initiative

[Kaspar Emanuel]

Sounds great Wayne, I'll give this some time to settle down and update this
thread when I have more to show.

On 13 January 2017 at 21:31, Wayne Stambaugh  wrote:

> On 1/13/2017 9:20 AM, Kaspar Emanuel wrote:
> >
> > On 13 January 2017 at 13:35, Wayne Stambaugh  > > wrote:
> >
> > Ithink using separate fields
> > would be cleaner and more reliable in the long run.
> >
> >
> > Yes, I am coming over to this point of view. I just quite liked the
> > compactness and clarity of the initial proposal but it might not be a
> > good trade-off to make in this instance.
> >
> > I think people tend to overcomplicate things a bit. These are just some
> > fields names that we all use but call different things.
> >
> > After a few weeks I will make a final document. It would be nice to put
> > up on kicad-pcb.org  somewhere to link to when
> > people ask about it suggested field names to use as defaults in their
> > application.
>
> We would have to decide that we want to make the part of the KiCad
> project before I would add it to the KiCad website.  Once you've nailed
> down the specification, let us know so we can discuss whether it makes
> sense to include it as part of the project.  I would want my library
> developers in on this discussion as well.
>
> >
> > On 13 January 2017 at 14:02, Clemens Koller  > > wrote:
> >
> > I am not sure how far you would go with KiCAD here and it's
> libraries.
> >
> >
> > I am not proposing to add anything to KiCAD at this point. Simply to
> > make a document that describes "standard" field names that the community
> > has agreed on. People can chose to use the standard if they wish.
> >
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Standard symbol field names initiative

[Wayne Stambaugh]

On 1/13/2017 9:20 AM, Kaspar Emanuel wrote:
> 
> On 13 January 2017 at 13:35, Wayne Stambaugh  > wrote:
> 
> Ithink using separate fields
> would be cleaner and more reliable in the long run.
> 
> 
> Yes, I am coming over to this point of view. I just quite liked the
> compactness and clarity of the initial proposal but it might not be a
> good trade-off to make in this instance.
> 
> I think people tend to overcomplicate things a bit. These are just some
> fields names that we all use but call different things.
> 
> After a few weeks I will make a final document. It would be nice to put
> up on kicad-pcb.org  somewhere to link to when
> people ask about it suggested field names to use as defaults in their
> application.

We would have to decide that we want to make the part of the KiCad
project before I would add it to the KiCad website.  Once you've nailed
down the specification, let us know so we can discuss whether it makes
sense to include it as part of the project.  I would want my library
developers in on this discussion as well.

> 
> On 13 January 2017 at 14:02, Clemens Koller  > wrote:
> 
> I am not sure how far you would go with KiCAD here and it's libraries.
> 
> 
> I am not proposing to add anything to KiCAD at this point. Simply to
> make a document that describes "standard" field names that the community
> has agreed on. People can chose to use the standard if they wish.
> 


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Standard symbol field names initiative

[Kaspar Emanuel]

On 13 January 2017 at 13:35, Wayne Stambaugh  wrote:

> Ithink using separate fields
> would be cleaner and more reliable in the long run.
>

Yes, I am coming over to this point of view. I just quite liked the
compactness and clarity of the initial proposal but it might not be a good
trade-off to make in this instance.

I think people tend to overcomplicate things a bit. These are just some
fields names that we all use but call different things.

After a few weeks I will make a final document. It would be nice to put up
on kicad-pcb.org somewhere to link to when people ask about it suggested
field names to use as defaults in their application.

On 13 January 2017 at 14:02, Clemens Koller  wrote:

> I am not sure how far you would go with KiCAD here and it's libraries.


I am not proposing to add anything to KiCAD at this point. Simply to make a
document that describes "standard" field names that the community has
agreed on. People can chose to use the standard if they wish.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Standard symbol field names initiative

[Clemens Koller]

Hello, Kaspar!

On 2017-01-13 12:50, Kaspar Emanuel wrote:
> Hi all,
> 
> I have started an initiative for external tools to agree on a few default 
> field names in schematics. Full details in the forum where you can also 
> propose amendments and register your preference.
> 
> https://forum.kicad.info/t/standard-symbol-field-names-initiative/4870

I am not sure how far you would go with KiCAD here and it's libraries.
I would keep things simple and _not_ add manufacturer information to the KiCAD 
libraries - divide and conquer!
Better split it up and link to all necessary information with a key/index in a 
database. (In my case it's 'partname', but it can become more complex: a 
combination of 'partname'+'value'+'instance')

I'll attach the Create code of my (still far away from perfect) database to 
give you an idea what maintainability hell you might run into if you keep 
everything inside of KiCAD, while KiCAD doesn't have a fully capable database 
frontend (yet ;-):

CREATE TABLE `main` (
`mfg` VARCHAR(45) NULL DEFAULT '' COMMENT 'mfg name',
`mfgname` VARCHAR(45) NULL DEFAULT '' COMMENT 'mfg partname',
`description` VARCHAR(255) NULL DEFAULT '' COMMENT 'functional 
specification',
`lycomment` VARCHAR(255) NULL DEFAULT '' COMMENT 'comment regarding 
part usage',
`partname` VARCHAR(45) NULL DEFAULT '' COMMENT 'KEY: partname_metric',
`partname_old` VARCHAR(45) NULL DEFAULT '' COMMENT 'KEY: 
partname_imperial (obsolete)',
`caedecal` VARCHAR(45) NULL DEFAULT '' COMMENT 'cae decal name',
`pincount` SMALLINT(5) UNSIGNED NULL DEFAULT '0' COMMENT 'no of package 
pins including e-pad, excluding drills',
`value` VARCHAR(20) NULL DEFAULT '' COMMENT 'ATTRIBUTE: primary 
component value',
`pcbdecal` VARCHAR(45) NULL DEFAULT '' COMMENT 'pcb decal name ',
`mfgpkg` VARCHAR(45) NULL DEFAULT '' COMMENT 'mfg package 
specification',
`mfgpkg_iec` VARCHAR(45) NULL DEFAULT '' COMMENT 'mfg package 
specification IEC',
`mfgpkg_jeita` VARCHAR(45) NULL DEFAULT '' COMMENT 'mfg package 
specification JEITA',
`mfgpkg_jedec` VARCHAR(45) NULL DEFAULT '' COMMENT 'mfg package 
specification JEDEC',
`power` DECIMAL(7,3) UNSIGNED NULL DEFAULT '0.000' COMMENT 'power 
rating',
`voltage` DECIMAL(7,3) UNSIGNED NULL DEFAULT '0.000' COMMENT 'voltage 
rating',
`current` DECIMAL(7,3) UNSIGNED NULL DEFAULT '0.000' COMMENT 'current 
rating',
`temp_min` SMALLINT(5) NULL DEFAULT '0' COMMENT 'min operating 
temperature',
`temp_max` SMALLINT(5) NULL DEFAULT '0' COMMENT 'max operating 
temperature',
`pitch` DECIMAL(7,3) UNSIGNED NULL DEFAULT '0.000' COMMENT 'footprint 
minimum pitch',
`length` DECIMAL(7,3) UNSIGNED NULL DEFAULT '0.000' COMMENT 'length of 
part',
`width` DECIMAL(7,3) UNSIGNED NULL DEFAULT '0.000' COMMENT 'width of 
part',
`height` DECIMAL(7,3) UNSIGNED NULL DEFAULT '0.000' COMMENT 'height of 
part',
`rohs` VARCHAR(10) NULL DEFAULT '' COMMENT 'rohs conformity',
`dista` VARCHAR(255) NULL DEFAULT '' COMMENT 'primary distributor',
`ordernoa` VARCHAR(255) NULL DEFAULT '' COMMENT 'orderno of primary 
distributor',
`minordera` INT(10) UNSIGNED NULL DEFAULT '0' COMMENT 'minimum order 
qty of primary distributor',
`currency` ENUM('EUR','USD','CAD') NOT NULL DEFAULT 'EUR' COMMENT 
'currency for all prices in this row',
`pricea1` DECIMAL(10,5) NULL DEFAULT '0.0' COMMENT 'price at one',
`pricea2` DECIMAL(10,5) NULL DEFAULT '0.0' COMMENT 'price at many',
`qtya2` INT(10) UNSIGNED NULL DEFAULT '0' COMMENT 'package size many',
`status` VARCHAR(10) NULL DEFAULT '' COMMENT 'general status if part is 
usable',
`available` VARCHAR(10) NULL DEFAULT '' COMMENT 'general status about 
part availability',
`stockqty` INT(10) NOT NULL DEFAULT '0' COMMENT 'in-house stock qty',
`extqty` INT(10) NOT NULL DEFAULT '0' COMMENT 'ext mfg stock qty',
`stockplace` VARCHAR(10) NULL DEFAULT '' COMMENT 'stock place',
`stockcomment` VARCHAR(100) NULL DEFAULT '' COMMENT 'stock comment',
`mfgcomment` VARCHAR(100) NULL DEFAULT '' COMMENT 'assembly house 
comment',
`tstamp` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE 
CURRENT_TIMESTAMP COMMENT 'timestamp of last update',
`grp` VARCHAR(45) NULL DEFAULT '' COMMENT 'part group',
`tqsap0` VARCHAR(45) NULL DEFAULT '' COMMENT 'mfg sap number 1',
`tqmat0` VARCHAR(100) NULL DEFAULT '' COMMENT 'mfg mat name 1',
`tqsap1` VARCHAR(45) NULL DEFAULT '' COMMENT 'mfg sap number 2',
`tqmat1` VARCHAR(100) NULL DEFAULT '' COMMENT 'mfg mat name 2',
`tqsap2` VARCHAR(45) NULL DEFAULT '' COMMENT 'mfg sap number 3',
`tqmat2` VARCHAR(100) NULL DEFAULT '' COMMENT 'mfg mat name 3',
`idx` INT(10) NOT NULL AUTO_INCREMENT COMMENT 'unique index',
UNIQUE INDEX 

Re: [Kicad-developers] Standard symbol field names initiative

[Wayne Stambaugh]

Hi Kaspar,

I applaud your efforts here but you should heed the warnings about using
a colon as a separator within a field.  I think using separate fields
would be cleaner and more reliable in the long run.

There are a lot of users who would like atomic symbols but no one can
ever seem to agree on what that really means.  This has been discussed
many times on this mailing list.  I wish you the best of luck in this
endeavor.  I have a feeling that you will need it.

Cheers,

Wayne

On 1/13/2017 6:50 AM, Kaspar Emanuel wrote:
> Hi all,
> 
> I have started an initiative for external tools to agree on a few
> default field names in schematics. Full details in the forum where you
> can also propose amendments and register your preference.
> 
> https://forum.kicad.info/t/standard-symbol-field-names-initiative/4870
> 
> Cheers,
> 
> Kaspar
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp