Having the design rules imported from eagle via a python script is the way to go IMHO. I don't see the benefit of adapting to a proprietary file format.
Having a warning shown is a better way than not starting up at all. I might have a look at it tomorrow. Cheers, Basti Am 31.08.2017 10:18 nachm. schrieb "Tomasz Wlostowski" < tomasz.wlostow...@cern.ch>: On 31.08.2017 19:59, Simon Küppers wrote: > Does it make sense to maybe use something like the EAGLE DRU Format? > Maybe make it fully compatible to it? Some fabs give you the EAGLE DRU File. > > Hi all, IMHO a warning on unrecognized token while parsing files is a must - in many cases users run nightlies to benefit from the latest features, but board manufacturers or companies run the stable release (due to IT restrictions or just worries about stability). Current situation makes this difficult (see complaints on the forum...) As for the DRU format - I wouldn't standardize on anything proprietary. Also Eagle's design rules are somewhat simpler than what we're aiming at in Kicad. Tom _______________________________________________ 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
