gEDA-dev: SoC Hopeful

["Bob Sherbert" <bob_dot_sherbert-at-NOSPAMgmail_dot_com>]

Hi all,
    Congratulations on getting into summer of code.  I'm applicant looking for some additional information  on one of the posted projects.  I apologize in advance if I'm posting to the wrong list for this; a polite redirection would be appreciated in such a case.
    My questions pertain to the project "Parts manager".  I understand the symbol/footprint chooser idea as well as the concept of a database backend for data sheets and additional information, these seem simple enough.  I am confused, however, by the lines: "In addition, this tool should be able to support multiple backend flows ... the parts manager should be able to also indicate how the symbol should be netlisted for spice, gnucap, or other backends."  From what I understand each type of backend has slightly different information requirements for a netlist file, and that it is perfectly possible to generate a schematic which may not meet all of the requirements for a given backend.  Does the quote indicate that the parts manager would be responsible for ensuring that all the required data for a given backend is present when the component is initially placed in the schematic?  For example: If a user selects a spice backend and then places a resistor, the parts manager should prompt the user for the footprint, a refdes(or auto generate one), and a value (with appropriate units).  Is my understanding of this (mostly) correct, and are there any major categories of information that I have overlooked that such a program would require?

Thanks for your time,
Bob Sherbert
Drexel University
Undergraduate Computer Engineering Major


_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev