I think this is a feasible solution. Having the possibility to import the values let's you create a database of manufacturing templates.
Am 31.08.2017 7:56 nachm. schrieb "José Ignacio" <jose.cyb...@gmail.com>: > I don't see why you couldn't have both, an embedded version of the actual > setup and the ability to import/export from/to an external file. > > On Thu, Aug 31, 2017 at 12:54 PM, Neal Hollingsworth < > nealanth...@gmail.com> wrote: > >> Hi all, >> I've mostly been lurking on the list, but thought I would make a >> suggestion regarding the via stack configuration. It might be nice to store >> the actual configuration/stack-up/DRC settings in an external file. The >> idea is that these are processes paraders that are deaigned to in most >> cases. This would make it possible have have e.g. A configuration file for >> a specific board house and price point. The board file would then only need >> to store a reference to the configuration file. Just a thought, take it for >> whatever it's worth! >> Neal Hollingsworth >> >> On Thu, Aug 31, 2017 at 12:44 PM Wayne Stambaugh <stambau...@gmail.com> >> wrote: >> >>> On 8/31/2017 1:21 PM, Bastian Neumannn wrote: >>> > Hi, >>> > >>> > I am currently building a feature that lets you input a via stack >>> > configuration. >>> > This information needs to be saved with the pcb data. So I tried >>> putting >>> > it into >>> > the kicad_pcb file. >>> > >>> > Now older versions will not load the file because it has additional >>> > values that >>> > it did not expect. >>> > >>> > How do you deal with that problem? >>> >>> The official policy is that file format changes must be backwards >>> compatible not forwards compatible. In other words, the user will have >>> to download the version KiCad where the change was made. >>> >>> If you make any changes to any of the file formats, you must increment >>> the file format rev number. This will cause the appropriate exception >>> to be raised which will warn the user the file version is newer than the >>> file version supported by the version of KiCad they are using. >>> >>> Since this is all very new and has not been planned for the stable 5 >>> release, I would most likely merge this into the master branch after the >>> stable 5 branch is created. >>> >>> Cheers, >>> >>> Wayne >>> >>> > >>> > Cheers, >>> > Basti >>> > >>> > >>> > _______________________________________________ >>> > 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 >>> >> -- >> Neal >> >> _______________________________________________ >> 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 > >
_______________________________________________ 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
