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=dTZ4UfH7mDbKCPx3i4QbFueiCLv9uICy/c+9/AUinwQ=;
        b=voy/LO1JCHfMkkURfCqudTfDJ115REHDpxxk7iNFgPhDoaBWg0kL6YEo4kZ9ENyd0+
         tGkqNxWkF/PdQANmf6PCev4/Yj8f5NCwSl3Jhd6wBaw4iVnqrTOsPJI/Vv9OGzjx0ioO
         a+BauUnpJgaT/ey40OGAmE7BPhaRebl6puD8hUks0Rmq1sF1lza6PagjLc5HJSO6tjmm
         vwwGWRX8aajLXEnSUksiXJok8R6qxY750yJg6yzZwoNLN2BsV3ivDNYYrIAnP1nUuD6J
         eAgcfZAl/q9B6uTxML5uOvSd4ojaaFJBFetFc/VEdvMXv9Y1bEONWNyHnaZ1JIpRwz6j
         H2YA==
MIME-Version: 1.0
X-Received: by 10.107.132.7 with SMTP id g7mr6335307iod.9.1436730721070; Sun,
 12 Jul 2015 12:52:01 -0700 (PDT)
In-Reply-To: <55A2BD04.6070400@ecosensory.com>
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>
	<55A2BD04 DOT 6070400 AT ecosensory DOT com>
Date: Sun, 12 Jul 2015 12:52:00 -0700
Message-ID: <CAOP4iL3VWCA-htMXR32jwvZNPBY0Boo0mHTAvOMFXY2d2-_szw@mail.gmail.com>
Subject: Re: developer excitement? was 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
Content-Type: multipart/alternative; boundary=001a113ecb9444757e051ab2f042
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

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

On Sun, Jul 12, 2015 at 12:16 PM, John Griessen <john AT ecosensory DOT com> wrote:

> On 07/12/2015 01:54 PM, 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 own
>> usage.
>>
>
> When would this rewiring happen?  In code? Compile time? Make files? Not
> sure I understand you.
>
> Do you mean redo the code parameters of the graphics part of gschem to
> handle other schematic-like uses?
> That might get more interest...unless GTK+ is "sooo passe" they won't
> abide it.
>


 Gschem/src would get a new subdirectory named schematic that would contain
all the current code for handling components, .sch and .sym files, wires
vectors attributes and hierarchy.  This could be copied to a new name and
used as a template for another tool. For example a finite state machine
tool would change the component code to handle states. A state is always a
circle rather than  a part loaded from a library. The wire code is changed
to use arcs instead of straight lines and they always terminate on a state
circle. The toolbar menus would change to remove any schematic menus and
replace them with FSM menus.

You would compile this into a new tool with a different name that used this
fsm module instead of the schematic one(make files).  The base code for
gschem would be a brain dead graphics tool like visio and all the smarts
would be added via modules.

John Eaton

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Sun, Jul 12, 2015 at 12:16 PM, John Griessen <span dir=3D"ltr">&lt;<=
a href=3D"mailto:john AT ecosensory DOT com" target=3D"_blank">john AT ecosensory DOT com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">O=
n 07/12/2015 01:54 PM, Ouabache Designworks (<a href=3D"mailto:z3qmtr45 AT gma=
il.com" target=3D"_blank">z3qmtr45 AT gmail DOT com</a>) [via <a href=3D"mailto:ge=
da-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>] wrote:<br=
>
</span><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><span class=3D"">
If you could extract all of the gschem schematic code and move it into a se=
parate module then any tool needing a graphics engine<br></span>
would only have to figure out how to rewire that module for their own usage=
.<br>
</blockquote>
<br>
When would this rewiring happen?=C2=A0 In code? Compile time? Make files? N=
ot sure I understand you.<br>
<br>
Do you mean redo the code parameters of the graphics part of gschem to hand=
le other schematic-like uses?<br>
That might get more interest...unless GTK+ is &quot;sooo passe&quot; they w=
on&#39;t abide it.<br></blockquote><div><br><br></div><div>=C2=A0Gschem/src=
 would get a new subdirectory named schematic that would contain all the cu=
rrent code for handling components, .sch and .sym files, wires vectors attr=
ibutes and hierarchy.=C2=A0 This could be copied to a new name and used as =
a template for another tool. For example a finite state machine tool would =
change the component code to handle states. A state is always a circle rath=
er than=C2=A0 a part loaded from a library. The wire code is changed to use=
 arcs instead of straight lines and they always terminate on a state circle=
. The toolbar menus would change to remove any schematic menus and replace =
them with FSM menus.<br><br></div><div>You would compile this into a new to=
ol with a different name that used this fsm module instead of the schematic=
 one(make files).=C2=A0 The base code for gschem would be a brain dead grap=
hics tool like visio and all the smarts would be added via modules. <br><br=
></div><div>John Eaton<br><br></div><div><br></div></div><br></div></div>

--001a113ecb9444757e051ab2f042--