Stuart Brorson wrote: >> You could hook it up to Kicad at that point. However, >> the focus should be on optimizing the common use case. > > In the best case, a default "right" command would be built into PCB, > but it could be user configurable via "edit -> properties". . . . I like this idea, Stuart. It defuses worries about losing customized makefile driven workflows.
>> Else, we can just store them in a list. Clicking an element in the >> list puts it in the paste buffer, pasting it removes it from the list. > > Naw. Personally, I hate the paste buffer. You don't know what's in > the paste buffer until after you paste it. Its contents are not > visible. Better is to have the footprints placed somewhere outside > the working area where the user can see them, and let the user drag > them onto the board. I like Stuart's active work area, and inactive margins idea a lot. >> Or is it an action script which contains specific verbs, such as "place >> component X", "delete component Y"? > > Yes. Also, verbs like > > (set_trace_width <X>); > (route_trace <X1, Y1> <X2, Y2>); This has some great high-level ideas. The schematic can have specs as attribs to say autoroute this trace, and leaving that off means it is going to be hand routed. Width tags being in the schematic is good for power versus signal routes. I really like this stuff. John Griessen -- Ecosensory Austin TX _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
