Seth,
This seems backwards to me. Geographical references are generated at
the board level so the references changes have to be pushed from the
board to the schematic not the other way around. This requires the
following steps:
1) Create a netlist from the board editor.
2 preferred) Send netlist via KiMail to schematic editor.
2 optional) Save netlist to file.
3 preferred) Update references in schematic from mailed netlist.
3 optional) Load netlist from file and update references in schematic.
Either way, the code will have to be written to generate a netlist in
the board editor and parse the netlist in the schematic editor. The
netlist generated by the board editor should have the same format as
the
netlist currently generated by the schematic editor.
The reason I am making this netlist approach a requirement is that this
will be necessary for pin and gate swapping, constraint management,
etc.
It will also allow us to replace the component assignment file (.cmp)
for updating footprint changes in the board. Allowing an interim
solution only means the someone will have to go back and merge it into
the netlist solution. I would rather avoid the extra work.
