X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type:content-transfer-encoding;
	bh=kZ7CTTDnU5TctzCCoeYYrfRbNcxuH5kqv1X9lT79bFw=;
	b=n9Ks0/2tHDXL2jkjulqRDDbuTbz/2WJHb+FgLKGmCiSTFOv5RuszPrShCni9iv/DPz
	lETzGKR7fKULOqvRHU7sW7XDfkOmZ8w5wnUjF/nHwujjIQzAj0bIlJ67Hz3GoB4Bugef
	Sl5wK8Uw6tFyBKjZyAD5z2REtVIP2e9cqZkHbwyraNlC5mhOz0vRFOOqDPPGpcbbR3tn
	LpR2VO6qEVIRI1AHpqMwq5QgpO00MUS34iPVLnrETCLqwxIEpxBZtUl7b+T/5uQN3h7+
	wpLri6TFDBpwriPWNdwb0vwVy/Z8k0QKDfQMAtxXbx7i1hynFMtZRhWkra09Ml51KjWK
	ehww==
MIME-Version:	1.0
In-Reply-To:	<43147C45-75A5-4393-AB07-AFBFD7BD09BA@noqsi.com>
References:	<20121204183305 DOT 6b04c0dc AT jive DOT levalinux DOT org>
	<20121208112649 DOT 388a9d22 AT jive DOT levalinux DOT org>
	<1355011808 DOT 19390 DOT 8 DOT camel AT localhost>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1212090407031 DOT 26605 AT igor2priv>
	<1355188647 DOT 12937 DOT 14 DOT camel AT localhost>
	<A7B4EDBD-3704-4837-9350-A16559C60A2A AT noqsi DOT com>
	<201212140010 DOT qBE0ABjV023762 AT envy DOT delorie DOT com>
	<172CCAAB-0423-43EF-8A04-5A9961F1D5B9 AT noqsi DOT com>
	<201212140122 DOT qBE1MoKM019255 AT envy DOT delorie DOT com>
	<5AA18F19-2EA9-4E7D-9378-F768D8E1E5DD AT jump-ing DOT de>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1212140501300 DOT 26605 AT igor2priv>
	<50CB5D82 DOT 8060507 AT jump-ing DOT de>
	<E5DE4486-B23F-4945-943A-F46C6E308B90 AT noqsi DOT com>
	<201212141820 DOT qBEIKQDN005665 AT envy DOT delorie DOT com>
	<43147C45-75A5-4393-AB07-AFBFD7BD09BA AT noqsi DOT com>
Date:	Fri, 14 Dec 2012 14:18:53 -0900
Message-ID:	<CAC4O8c_YzeqQ84huGrZPL+=aK5C89phD3VgRHko40N8hWCzw7A@mail.gmail.com>
Subject:	Re: [geda-user] Find rat lines
From:	Britton Kerin <britton DOT kerin AT gmail DOT com>
To:	geda-user AT delorie DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id qBENIvYm012632
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Fri, Dec 14, 2012 at 10:29 AM, John Doty <jpd AT noqsi DOT com> wrote:

Hi John, first my two cents on tagging, I agree with you (and everyone else
it seems) that its a good idea in principle, but its going to have some
troubles in practice.  I end up working from the middle of wires a lot, and
copying chunks of wiring around.  As Pete noted many of these already tedious
operations would get a lot more tedious if pcb was constantly bugging you to
retag things.  A short is the uncommon case for clone and clone-and-modify
use cases, so you don't want to pay for short detection too much as you work.
So lumped short detection later on still comes out useful.

Tagging would get a lot more useful if pcb had some neat overall way to capture
clone and clone-and-modify use cases, but its hard to see how to do this.

> In my experience with pcb, it's all punishment and confusion. It's impossible to get the program to do anything *simple*. Instead, it tries to read the user's mind, frequently getting it wrong. And it isn't just me: a couple of years ago I had an experienced professional engineer working for me. One of his tasks was learning pcb (I was thinking, OK, maybe it's just one of those things a simple-minded physicist can't get). He failed.
>

I find this really surprising, since for me pcb was the simple part of gEDA
to learn.  It was the combination of figuring out which attributes had to
be set in gschem, how symbols and footprints connected together, and how
the whole arrangement was propagated into pcb that was painful.

Since you don't use pcb, I'm curious: is it pcb itself that causes confusion,
or are the above issues bothering you and/or this other engineer?

Britton

- Raw text -