← Back to team overview

kicad-developers team mailing list archive

Re: Pcbnew file format

 

We should definitely coordinate this work.  I thought Jon's drc work
saves the drc settings in a separate drc file for portability between
projects.  If that is the case, we should avoid adding new drc settings
to the board file.

On 7/3/2019 1:46 PM, Seth Hillbrand wrote:
> Hi Jeff-
> 
> Can we split out the DRC things?  I'm pretty sure that these are
> included in Jon's DRC rework, so it would be nice to avoid a temporary
> file format that we supersede shortly.
> 
> -S
> 
> 
> On 2019-07-03 06:23, Jeff Young wrote:
>> Please see
>> https://git.launchpad.net/~jeyjey/kicad/commit/?id=a2c2d9f5d9b37576ec72cd0d4c64652cfddeb8df
>>
>> for board file changes for:
>>
>> 1) min-hole-to-hole distance
>> 2) courtyard DRC flags (require courtyards and prohibit overlapping
>> courtyards)
>> 3) default layer line widths and text dimensions
>>
>> Cheers,
>> Jeff.
>>
>>> On 2 Jul 2019, at 16:58, Wayne Stambaugh <stambaughw@xxxxxxxxx>
>>> wrote:
>>> On 7/2/2019 11:11 AM, jp charras wrote:
>>> Le 02/07/2019 à 16:55, Jeff Young a écrit :
>>> I was testing 5.1 and noticed that it can no longer open 6.0 files.
>>> Was this accidental, or have we now diverged?
>>>
>>> (I ask only because I have a bunch of fixes waiting for file format
>>> changes which I could go ahead and make if we have officially
>>> diverged.)
>>>
>>> Cheers,
>>> Jeff.
>>>
>>> There is at least a change: "max_error" param in "setup" section.
>>>
>>> I have myself some other changes waiting in file format to support
>>> zones
>>> filled without outline thickness, and a support for board stackup
>>> info
>>> (for manufacturing purposes)
>>
>> Since the board file format in the master branch is no longer
>> compatible
>> with the 5.1 branch, I don't see any issues with pushing file format
>> changes.  I only ask that before you push commits that affect the file
>> format, please post your changes so we can take a look at them so we
>> can
>> review the file format changes before we merge them.  Please be sure
>> to
>> keep the file version up to date correctly as you push your individual
>> changes to prevent any user issues.
>>
>> Cheers,
>>
>> Wayne
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp


Follow ups

References