On Dec 9, 2008, at 10:59 PM, Duncan Drennan wrote: >> I wonder if it will still be possible to script gschem from the >> cygwin >> command window in the case. (And I'll ask you to test it when it is >> available). If not, I'll perhaps have to offer a gschem_cmd.exe >> variant >> which doesn't detach from the console. > > For the testing I am actually using mingw so I am scripting from the > Windows command prompt (FYI I am running Vista). > > The issue of printing schematics is going to be one which just about > every Windows user is going to bump their head against. The concept of > running scripts (or even programmes) from a command prompt is just not > a part of most users paradigms - even engineers, to my surprise.
gEDA's a flexible toolkit that supports multiple flows. Scripting is a critical part of this. Anyone who can't do scripting is going to be in for endless frustration: printing is just a tiny issue. > Getting a multipage schematic print out from gschem is a (relatively) > complex task. Nah. And how are you going to fix this? For example, how do you decide *which* pages belong to *which* schematic? With gEDA, make, and other tools, it's easy to assemble project documentation, as comprehensively as the project needs. That's much more power than just being able to simply print schematics. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ [EMAIL PROTECTED] _______________________________________________ geda-dev mailing list geda-dev@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
