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:date:message-id:subject:from:to:content-type;
	bh=GGs5WToiFWfuSl4cH76jZDwoTQ9p7zfll576pQaphRE=;
	b=Af/2S4lJun2H8z58Y8YuJ9DKWnFrI0ShT96DeI2h9eb1NHRBzFIisDvv6rE/QcEyAH
	+rfRI4nagwReA3n3oXy7kwRlTQIyMlPcE4zZwph3EhUOGZMd4d1ioLoSnWOkKmo+Fzg9
	lyz9nNrXzyL38VXUNTpYxmkLj4gRjRDp3Gw4l3irgaLua3YXCADHgev+YXJ7IV/Hl/SL
	CcWySbiZ5XWvKYHlUpC0Fanw+Di/00mThqTdvNXcgfqobNky+Cbl66H86tDhNb/zYUdi
	ibVMNovFVO3Yo4XYDzZ4GN+QBV+y+rjl7MrOX5iPA3mHkVfvK8LqRRgrtNy6dImyM939
	FhZA==
MIME-Version:	1.0
X-Received:	by 10.180.93.168 with SMTP id cv8mr4506642wib.54.1443915896965;
	Sat, 03 Oct 2015 16:44:56 -0700 (PDT)
Date:	Sat, 3 Oct 2015 15:44:56 -0800
Message-ID:	<CAC4O8c-R3KdTx66MS4i2Pwn2eC=LyHHiYdebF=KhZvsjf9bnEg@mail.gmail.com>
Subject:	[geda-user] what does gEDA need to achieve easy sharing of designs?
From:	"Britton Kerin (britton DOT kerin 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

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

Hi guys, I guess this is sort of my blue-sky turrn, sorry.  It's just stuff
that I think it might be useful to have in mind.

So far as I'm aware at the moment, the only real sharing of gEDA designs is
via gedasymbols (which I confess I've never even used, since I ended up
with my own incremental heavy-symbols approach).

A public forum for sharing of schematics/layout doesn't exist so far as I
know.

So what would need to happen for this to become possible?  Some other
projects are starting on this and so far a I know it's sort of a first, how
can gEDA provide it?

Random thoughts on the subject:

* gEDA isn't about to become a browser editor, we can all accept that.  But
it would be nice if things generated with gEDA could be easily cataloged,
viewed, and shared somehow.

* One major barrier to sharing is that everyone has a different strategy
for creating parts.  Might it be possible to fit these different approaches
behind a common interface, thereby rendering them more accessible and
comprehensible?  For true design sharing, the sources should be accessible

* A while back I remember someone made IIRC a way to pack symbols into a
.sch, I never got around to looking at it at the time and don't know where
it is now?  I don't remember enough keywords to go find it.

* Is there a way of doing subcircuit layout that would work widely enough
to be promoted as a semi-standard?  This is a big can of worms of course
especially if one considers parametric designs or custom layer assignments,
but it shouldn't be impossible.  How could we start on this?

There's some good stuff happening with gEDA at the moment.  Perhaps the
biggest win of all would be if we go to the point where common subcircuits
didn't need to be reinvented by everyone.
I mean the topo-router excites the bejeebers outa me but there might be
even bigger efficiency wins from less sexy work -- provided it went far
enough to be effective.

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

<div dir=3D"ltr"><br><div style=3D"">Hi guys, I guess this is sort of my bl=
ue-sky turrn, sorry.=C2=A0 It&#39;s just stuff that I think it might be use=
ful to have in mind.</div><div style=3D""><br></div><div style=3D"">So far =
as I&#39;m aware at the moment, the only real sharing of gEDA designs is vi=
a gedasymbols (which I confess I&#39;ve never even used, since I ended up w=
ith my own incremental heavy-symbols approach).</div><div style=3D""><br></=
div><div style=3D"">A public forum for sharing of schematics/layout doesn&#=
39;t exist so far as I know.</div><div style=3D""><br></div><div style=3D""=
>So what would need to happen for this to become possible?=C2=A0 Some other=
 projects are starting on this and so far a I know it&#39;s sort of a first=
, how can gEDA provide it?</div><div style=3D""><br></div><div style=3D"">R=
andom thoughts on the subject:</div><div style=3D""><br></div><div style=3D=
"">* gEDA isn&#39;t about to become a browser editor, we can all accept tha=
t.=C2=A0 But it would be nice if things generated with gEDA could be easily=
 cataloged, viewed, and shared somehow.</div><div style=3D""><br></div><div=
 style=3D"">* One major barrier to sharing is that everyone has a different=
 strategy for creating parts.=C2=A0 Might it be possible to fit these diffe=
rent approaches behind a common interface, thereby rendering them more acce=
ssible and comprehensible?=C2=A0 For true design sharing, the sources shoul=
d be accessible</div><div style=3D""><br></div><div style=3D"">* A while ba=
ck I remember someone made IIRC a way to pack symbols into a .sch, I never =
got around to looking at it at the time and don&#39;t know where it is now?=
=C2=A0 I don&#39;t remember enough keywords to go find it.</div><div style=
=3D""><br></div><div style=3D"">* Is there a way of doing subcircuit layout=
 that would work widely enough to be promoted as a semi-standard?=C2=A0 Thi=
s is a big can of worms of course especially if one considers parametric de=
signs or custom layer assignments, but it shouldn&#39;t be impossible.=C2=
=A0 How could we start on this?</div><div style=3D""><br></div><div style=
=3D"">There&#39;s some good stuff happening with gEDA at the moment.=C2=A0 =
Perhaps the biggest win of all would be if we go to the point where common =
subcircuits didn&#39;t need to be reinvented by everyone.</div><div style=
=3D"">I mean the topo-router excites the bejeebers outa me but there might =
be even bigger efficiency wins from less sexy work -- provided it went far =
enough to be effective.</div><div style=3D""><br></div></div>

--f46d043c7fba1fd36805213bde44--

- Raw text -