Mail Archives: geda-user/2014/10/19/04:06:41
On Sat, 18 Oct 2014, Evan Foss wrote:
> it does the job well. Sorry workflow was the wrong word. I was just
> wondering if like diff there was something obvious missing in the
> toolchain.
I think the obvious thing missing is integration between schematic capture
and PCB layout, and both with the desktop environment. I've already
griped here on the list about diodes getting reversed, and I won't
belabour that beyond saying that it's a dealbreaker. But we also have
different hotkeys for the two GUIs; hotkeys in both that conflict, both in
specific details and in general approach, with the conventions of desktop
environments (e.g. using sequences of unshifted alphabet letters where
everything else on my desktop would use Ctrl or Alt; *not* accepting the
Delete key for "delete", deleting something near the mouse cursor (chosen
at random if there is more than one such thing!) instead of the thing that
is selected, etc.); the need to run a separate converter program and then
load three separate files manually, in the right order, one of them by
typing a scripting language command into a command line, just to get one
schematic into pcb; and so on. Attempting to use gschem or pcb doesn't
just have a learning curve. It requires actively unlearning the rules
that other GUI programs follow. And attempting to use either of them
after using the other requires unlearning the many points on which they
conflict.
If you want yet another separate un-integrated program to add to the
system, something to improve back-annotation from pcb to gschem seems like
an obvious gap in the current system.
Integration doesn't have to mean everything must be done by a single huge
GUI program. We can have lots of separate single-task utilities - and we
should, the success of Unix demonstrates why. But they should all be able
to really work together without requiring the user to manually compensate
for the conflicts between the different pieces of software.
The gEDA FAQ contains a fair bit of text attempting to justify why a lack
of integration is really better. With respect, it is wrong. The fact of
poor integration is easily understandable from the history of the system,
and it may not be easy or possible to solve it given volunteer resource
limitations, but it is a CATASTROPHIC PROBLEM, not a positive selling
point. And the fact that this is a frequently-asked question suggests a
significant number of users are looking for integration and being turned
away because gEDA doesn't have it.
--
Matthew Skala
mskala AT ansuz DOT sooke DOT bc DOT ca People before principles.
http://ansuz.sooke.bc.ca/
- Raw text -