The bottom line question for the core developers is: What prevents us from writing a file of Guile functions and adding a line to gafrc to load it and get this functionality?
On Nov 19, 2009, at 1:53 PM, Henry Von Bank wrote: > > After a symbol is placed in the schematic an attribute should be > specified that points to another file containing component or other > info. This would be equivalent to an import/include statement. It > should probably just be limited to one of these statements per object, > although you could make a case (see below) for allowing multiple ones > of these. Also note that when in the design process you specify this > attribute would depend on your workflow. The problem here is that this approach interferes with hierarchical design, where some attributes will depend on which expanded instance you have. This is especially true if you have a parameterized hierarchical block. Of course, the present approach has these problems, too. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ [email protected] _______________________________________________ geda-user mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
