On Apr 22, 2010, at 1:44 PM, Madhusudan Singh wrote: > That was really uncalled for.
I'm sorry you feel that way. > > I was talking about symbol definitions, and not gnetlist. They are deeply connected. The symbol definition depends on the downstream flow, and gnetlist is a major agent of that flow. There is no "correct" symbol definition that is independent of the way you are using the symbol. The gnetlist back end is responsible for grabbing the attributes from the schematic and either interpreting them or passing them along to the next stage, as needed. Which back end you choose determines which attributes matter, and to some extent how they will be interpreted. While the relatively "light" symbol definitions in the standard library are suitable for a variety of flows, they usually lack the specialized attributes (like model-name) needed for a specialized flow (like ngspice via the spice-sdb gnetlist back end). Please try to understand that gEDA isn't an integrated tool that forces you into a particular flow. It's a versatile toolkit. That perhaps puts a burden on you when you're starting out, but is richly rewarding once you have libraries and processes customized to your needs. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ j...@noqsi.com _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
