X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Virus-Scanned: amavisd-new at cloud9.net
Date: Mon, 4 Aug 2014 07:48:36 -0400 (EDT)
From: Stuart Brorson <sdb AT cloud9 DOT net>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Silkscreened component values, mailing list, and
 gEDA development
In-Reply-To: <20140804103927.GF24580@localhost.localdomain>
Message-ID: <alpine.BSF.2.00.1408040741380.227@earl-grey.cloud9.net>
References: <alpine DOT LNX DOT 2 DOT 02 DOT 1406291518550 DOT 30669 AT localhost DOT localdomain> <1404129760 DOT 16971 DOT 8 DOT camel AT pcjc2lap> <4F3EB7F5-6600-4ED1-9DD0-9333AED9CC9A AT noqsi DOT com> <20140804103927 DOT GF24580 AT localhost DOT localdomain>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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
Precedence: bulk

Hi --

>> Many symbol creators don?t seem to
>> understand pinseq.
>
> For SPICE, I'm thinking of using a unique attribute, say "pinnode". So we
> could part the two workflows - simulation in SPICE and making pcb's.
> I believe that in general every particular workflow should lean on its
> own attributes in gEDA/gaf.

Overloading pinseq for use with spice-sdb seems to have caused a lot
more grief than I could have imagined at the time.  I think the idea
of separating the workflows makes sense.  Moreover, eliminating the
overload would be a good thing.  I would do it be modifying spice-sdb
to use a different atribute, for example pinnode, as you say.  Or
spicepin, or something like that.

The only question is, how many legacy schematics would you break?
IMO, I don't think that many folks keep gEDA simulations going for
years and years.  And those who do are very clueful and will know how
to fix their spice schematics using grep and other tools.  Therefore,
breaking legacy work is probably not a show stopper.

I say, go for it.

Stuart
Original spice-sdb developer.