On Friday 23 November 2007, Peter TB Brett wrote: > We already have it: Not really ...
> (1) Write a Scheme function which does what you need > (2) Add it to menu definitions in system-gschemrc Let's think of the "export" procedure .... you save the schematic, go out to a shell and type something like: "gnetlist -g spice-sdb ......" What does that mean? "-g" means "run a guile script". What's a "guile script"? etc .... What we need is a simple way to define a menu .. Think about an "export" menu. I want to see a menu listing the formats .. spice pcb verilog vhdl pdf ps ... and for a user who can't program in any language to be able to edit a simple file to add more .. How about this simple file: ======= ~/.gEDA/menu-export.cfg ======== ## menu export spice fxs "gnetlist -g spice-sdb $$" pcb fxp "gsch2pcb $$" verilog fxv "gnucap-trans --in gschem --out verilog $$" vhdl fxh "gnetlist -g vams $$" .......etc..... ============ Suppose I want to add a top level "simulate" ... We have a file: ====== ~/.gEDA/menu-top.cfg ======= ## menu top File "" menu file Edit "" menu edit Buffer "" menu buffer ..... Attributes "" menu attributes Options "" menu options Help "" menu help ========= So, I edit the file to add a line,... ====== ~/.gEDA/menu-top.cfg ======= ....... Attributes "" menu attributes Simulate "" menu simulate Options "" menu options Help "" menu help ========= and a new simulate menu: ====== ~/.gEDA/menu-simulate.cfg ====== ## menu simulate gnucap-gspiceui sgg "gspiceui -s gnucap -g spice-sdb $$" gnucap-CL sgg "gnetlist -g spice-sdb $$ -o $$.ckt; gnucap $$.ckt" ======== Paul ..... Is this what you were thinking of? _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
