X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Sun, 12 Jul 2015 21:58:50 +0200 (CEST)
From:	Roland Lutz <rlutz AT hedmen DOT org>
To:	"Ouabache Designworks (z3qmtr45 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject:	Re: developer excitement? was Re: [geda-user] gEDA/gschem still
	alive?
In-Reply-To:	<CAOP4iL2GjggOYaZK+zpmt2na50iH57bh=+mK5pHfj=kPjqvGcw@mail.gmail.com>
Message-ID:	<alpine.DEB.2.11.1507122143560.10458@nimbus>
References:	<CAM2RGhTpfbqM7zNn72TBOjeL7B7LPT1PxSEU3+9aDdChFrPFTg AT mail DOT gmail DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1507090507530 DOT 6924 AT igor2priv> <CAC4O8c_9mvUW6ub2EWCs2boucLdnzj5O_xCsaCNEaT17brLe0g AT mail DOT gmail DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1507091922140 DOT 6924 AT igor2priv>
	<CAC4O8c9jPo_wbpk2xnzGr6+Gdg0OFSBPyA-FYHjn_pE1PehZog AT mail DOT gmail DOT com> <55A229D3 DOT 3080501 AT zoot DOT drehmel DOT com> <55A29426 DOT 8080908 AT xs4all DOT nl> <alpine DOT DEB DOT 2 DOT 11 DOT 1507122008480 DOT 4570 AT nimbus> <CAOP4iL2GjggOYaZK+zpmt2na50iH57bh=+mK5pHfj=kPjqvGcw AT mail DOT gmail DOT com>
User-Agent:	Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version:	1.0
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 Sun, 12 Jul 2015, Ouabache Designworks (z3qmtr45 AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> If you could extract all of the gschem schematic code and move it into a
> separate module then any tool needing a graphics engine would only have to
> figure out how to rewire that module for their onw usage.

Are you aware of Dan McMahill's cascade analysis program[0]?  It uses 
custom gEDA symbols ("Cascade simulation elements" in the default library) 
and an associated gnetlist backend (gnet-cascade.scm) to produce the 
analysis program's input files.

Actually, there is little code in libgeda/gnetlist which is specific to 
"electronic schematics" (in the lack of a better word).  Apart from naming 
conventions like "netname", it's IIRC just the fact that all components 
with a common refdes are treated as a single "package" during netlist 
generation.  (If you aren't using this feature, you'll have to set an 
individual refdes for each component.)

Roland


[0] http://rfcascade.sourceforge.net/

- Raw text -