Jason wrote:
Chris Cole wrote:
Just curious, why not include xgsch2pcb functionality inside of
gschem?
As an aside, the first thing that lept to mind, was the Unix
philosophy of "one tool, one job." So, I started digging to find
where it came from. It's one of those "quoted all over the place,
but no origin to be found" kind of phrases.
The best I could find was this [1], which sums it up nicely.
I personally don't use xgsch2pcb. I run gsch2pcb from a Makefile,
but that's my personal preference. I prefer to script jobs that
shouldn't need to be interactive. ymmv.
I personally don't use xgsch2pcb either (I might if it were part of
gschem)... I'm definitely a script jockey too, but sometimes I like
to look at things from the perspective of those who can't / won't be
script jockeys. You know, the kind of people who are used to using
windows software and don't want to have to drop into a shell every 5
seconds to run commands. I think the Unix design philosophy is nice
for programs designed to be run strictly from the command line -- but
I think the line blurs a tad-bit when you cross over into a UI-based
programs. What's the workflow for a Windows-based EDA program like
Eagle?