gEDA-dev: gnetman inspired libgeda datastructures

[John Griessen]

Peter Clifton wrote:

> We consider "net" to be electrical - rather than graphical, with
> "NetSegments" being the graphical representation. Similarly, "pins" are
> the graphical representation of an "Mport" (master port). 



> Because it makes more sense to associate attributes with electrical
> entities such as the nets, or Mports, rather than graphical entities,
> attributes will be stored as abstract data rather than graphical
> constructs as at present. When text is required on a Page or Symbol (two
> closely related entities), literal text may be entered, or a reference
> made to attribute data from the current circuit - or lower in the design
> tree.
> 


Does the above infer that you always first create a netlist from newly defined graphical "NetSegments",
then you have defined your nets electrically if they pass self consistency checks, then
and only then can you reconcile mports with nets?     Sounds fine to me -- and implies
always on netlisting function.   When you edit a sub schematic and change its mports, it will cause the higher schematic to be 
broken.   We will need a way to handle that without confusion -- the netlister may need to go from the bottom up, and stop when it 
hits trouble, and still be able to use its partial results for the hierarchy from here down...

John Griessen