kicad-developers team mailing list archive

[Greg Smith <ecomputerd@xxxxxxxxx>]

To assist compilation of a set of rules, we might be able to use this link to my effortson loading/saving an Eagle DRU file. I've listed all the settings saved by the Eagledesign rule check dialog, and annotated the output file. I list the equivalent DRU keywordwith its associated dialog entry box (including the help text within the dialog box):https://forum.kicad.info/t/design-rules-file-load-save/7044/21

Some of the DRCs do not transfer because of the difference in the specific checks available.There really should be a distinction between the two major types of design rules:1) settings that are assigned to tools and go into the layout as it is placed2) settings that are checked after layoutAlthough, perhaps obviously, some are both.
An easy (?) example is the Global Design Rules (Type 2) vs. Local Clearance Settings (Type 1 and a little Type 2).
 

    On Wednesday, August 23, 2017 7:55 AM, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
 

 On 8/23/2017 8:49 AM, Tomasz Wlostowski wrote:
> On 23.08.2017 14:05, Wayne Stambaugh wrote:
>> This is the missing piece of the puzzle.  We would need to create a
>> constraints manager to handle a list of constraints which could either
>> be an internally defined constraint or a custom python constraint.
>> Without a well defined interface, this would be a mess.
> 
> If I may add my 5 cents: no python please for any *critical*
> functionality of Kicad, like the DRC. I can only imagine expensive
> boards coming back from production because somebody didn't have python
> DRC plugins installed/configured.

Agreed, that is why I suggested python for custom stuff.  All standard
constraints and checks would be written in C++.

> 
> Concerning new DRC plans - a rewrite of DRC is in the V6 roadmap:
> 
> ----
> 
> Design Rule Check (DRC) Improvements.
> 
> Goal:
> 
> Create additional DRC tests for improved error checking.
> 
> Task:
> 
>    Replace geometry code with unified geometry library.
>    Remove floating point code from clearance calculations to prevent
> rounding errors.
>    Add checks for component, silk screen, and mask clearances.
>    Add checks for keep out zones.
>    Remove DRC related limitations such as no arc or text on copper layers.
>    Add option for saving and loading DRC options.
> 
> ----
> 
> We need specifications for both the constraint manager & the DRC checks
> to be implemented. Would anybody here volunteer to write the specs or
> design the UI?
> 
> Cheers,
> Tom
> 

_______________________________________________
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