Mail Archives: geda-user/2015/07/09/19:59:55
On Jul 9, 2015, at 5:32 PM, DJ Delorie <dj AT delorie DOT com> wrote:
>
>> How do you think this mapping tool should get the data from the schematic -
>> via a special scheme netlist script or by reading the schematic file itself?
>
> Nothing should read the schematic itself. I thought of two ways:
>
> 1. The various tools that deal with attributes also know about
> "implied" attributes, which are the result of database and ruleset
> queries. Thus, in gschem's attribute window you'd have access to
> the database as well as user-specified attributes.
But it shouldn’t be in gschem. This is downstream, and there may be multiple streams from the same schematic. I have schematic pages that wind up as part of two different board designs in four downstream flows (Osmond, Allegro, PADS, and ngspice). Different footprints in prototype and production versions, also.
> This lets the
> user override the rules while still having the convenience of a
> database.
>
> 2. The netlister would need to feed its data into some sort of engine
> that combines the specific attributes with implied ones, adds in
> other external data and/or back-annotation data, and produce
> whatever the backend needs.
>
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
- Raw text -