On 10/19/07, Peter TB Brett <[EMAIL PROTECTED]> wrote: > Case study 1 > ============ > > Peter is developing a new device using gEDA, and want to use an external > layout contractor (who also uses gEDA & PCB). Peter wants to package up his > schematic to send off to the contractor, but has several non-standard system > libraries as well as some project-specific symbols. > > Current model: Peter is an expert, so he is able to spend a few hours and use > some complicated shell scripts to hunt down every relevant symbol and > organize them into a new directory before manually checking through that the > correct symbols have been selected and that nothing has been broken. He then > tars the assemblage up before sending it to the contractor. The contractor > untars the files, and (if Peter was successful) can then use the schematic. > > Proposed model: Peter sends his schematic file to the contractor. The > contractor double-clicks on it, and it opens in gschem in fully editable and > consistent glory.
This would be very convenient. As long as the contractor has gschem s/he can immediately use the schematic. No utilities. No configuration files. Just one .sch file and you are done. (* jcl *) -- http://www.luciani.org _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user