X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-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;
	bh=d39QQGPHDV1i5BrONaGHYnFJ5jlr0xSiVYJpsDF73c0=;
	b=FEzF8bMKIhKg0ufSusAoGwRERJrqSrK/eyVTt88+26gTfYSpChoehiqiCWlfMILDob
	enJFBXFAD6t+4lXkWO/E59vkHjggs2irCKAbfaE4mUyd/IJzDBiAJID8sJuB5ceRpNP6
	72gblLH+5DaXfHtR/E+6NXWAgyrvvU9zeqRuPDFuA5E99BYatcZHyA2ZqbZNgdi3Q8+3
	eTU45CPtV7OU3ey1b4o38U8TRal7AsmIKrX98Z/++9dknAOAHGja//FvZk6J9YpgDsmn
	xA7lRzNgPpDJNugKKAYGKqx5w5JCW77byR94WGMTvhT9FSTSl8Xjy/BYA9iXxLFFyzDy
	BbTw==
MIME-Version:	1.0
X-Received:	by 10.50.225.40 with SMTP id rh8mr51115483igc.39.1436282679488;
	Tue, 07 Jul 2015 08:24:39 -0700 (PDT)
In-Reply-To:	<20150707060409.GB14357@localhost.localdomain>
References:	<1435510363 DOT 682 DOT 26 DOT camel AT ssalewski DOT de>
	<20150703030409 DOT 32398 DOT qmail AT stuge DOT se>
	<CAFC5WMoa2-z6bNca_bQN+jmMR260UBmoJQybUzH=L2TrBpzNNA AT mail DOT gmail DOT com>
	<1436006726 DOT 677 DOT 13 DOT camel AT ssalewski DOT de>
	<20150706200609 DOT GD24178 AT localhost DOT localdomain>
	<CAC4O8c9f0pLsLu_dyuO5ggh7RmHY1vAA=UUhk9AE0JYZb4mhBQ AT mail DOT gmail DOT com>
	<CAM2RGhQfPO31-1Uyc3kC7w286r0VD7c41UZEZcyYquzknCxbsQ AT mail DOT gmail DOT com>
	<20150707060409 DOT GB14357 AT localhost DOT localdomain>
Date:	Tue, 7 Jul 2015 08:24:39 -0700
Message-ID:	<CAOP4iL2C_LU=RQy5FWYF-7RrHW6tqhqqyFJGjkwLQ2AD7FiYJA@mail.gmail.com>
Subject:	Re: [geda-user] gEDA/gschem still alive?
From:	"Ouabache Designworks (z3qmtr45 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
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

--001a11c3a6e2e88bd1051a4a9e68
Content-Type: text/plain; charset=UTF-8

Rather than concentrating on what we don't like, I wonder if anyone can
point to a FOSS Eda tool out there that you do like. What did they do right
and what languages did they use?


What I would like to do is to step back and look at the big picture as to
where and how we can use a schematic capture tool in todays world. Things
have changed a lot since the 1980's and some things that we did back then
no longer work. One example is search paths. If you look in the default
symbol library setup then you will see that some libraries are commented
out due to name collisions. What happens when you get a new library that
collides with an existing one and commenting out is not an option?
We need to come up with a solution before our users run into that problem.

gEDA currently defines a dot_sch schematic file and a dot_sym symbol file
as our interchange formats. These are read into gschem and stored in some
internal data structure that gschem manipulates before it is written out
in  a save operation. Why not use a FOSS data base instead of internal
memory?  If PCB also used the same database then cross probing and back
annotation become easier.

Brain storming anyone?


John Eaton

--001a11c3a6e2e88bd1051a4a9e68
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra">Rather than concentrating o=
n what we don&#39;t like, I wonder if anyone can point to a FOSS Eda tool o=
ut there that you do like. What did they do right and what languages did th=
ey use?<br><br><br></div><div class=3D"gmail_extra">What I would like to do=
 is to step back and look at the big picture as to where and how we can use=
 a schematic capture tool in todays world. Things have changed a lot since =
the 1980&#39;s and some things that we did back then no longer work. One ex=
ample is search paths. If you look in the default symbol library setup then=
 you will see that some libraries are commented out due to name collisions.=
 What happens when you get a new library that collides with an existing one=
 and commenting out is not an option?<br></div><div class=3D"gmail_extra">W=
e need to come up with a solution before our users run into that problem.<b=
r><br></div><div class=3D"gmail_extra">gEDA currently defines a dot_sch sch=
ematic file and a dot_sym symbol file as our interchange formats. These are=
 read into gschem and stored in some internal data structure that gschem ma=
nipulates before it is written out in=C2=A0 a save operation. Why not use a=
 FOSS data base instead of internal memory?=C2=A0 If PCB also used the same=
 database then cross probing and back annotation become easier. <br><br></d=
iv><div class=3D"gmail_extra">Brain storming anyone?<br><br><br></div><div =
class=3D"gmail_extra">John Eaton<br><br></div><div class=3D"gmail_extra"><b=
r><br><br></div><div class=3D"gmail_extra"><br></div></div>

--001a11c3a6e2e88bd1051a4a9e68--

- Raw text -