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:content-transfer-encoding;
	bh=uWMSb37RZHNet6nnOBkcbl5suj7r+tDbVVeaVtqO7gA=;
	b=alc8q0i1wWg3IsxRQLxpcztM5CpcWwvm0uTUFbNeeYGGyB/QsYhbLKGCVPTbRdYkY9
	e+Nl3WFeNMDiM+ltnMcWp+3OwA34vxxqywtyYrpHMTCdeALn/afVPvDDcPEMF1qAI25v
	Zy3aN+bcbwJI5zBZP0NsfOjKbcA7Jp12apIHwA2BpBgybwTBOGIK5KKNTjmPudg4OlLO
	R0llhDALqVq9kTjyjeyFFBfXHZa8u5m104cOhCVIB5chplllCuDZCRZzzb/Z8vm9FQPP
	NSqpiHMm/xgot0I+/HN0Q9pQdLDUKXf15VcU1Xtxgj3mqctXdEbAcipyy1YvsoT7G54D
	Wviw==
MIME-Version:	1.0
X-Received:	by 10.152.21.37 with SMTP id s5mr20884256lae.2.1435695101836; Tue,
	30 Jun 2015 13:11:41 -0700 (PDT)
In-Reply-To:	<CAM2RGhR4LKmT7ko19fU_j_ThkqjmiHGNDLsvE+HrVqCYj=ANdQ@mail.gmail.com>
References:	<1435510363 DOT 682 DOT 26 DOT camel AT ssalewski DOT de>
	<55902AB9 DOT 9000004 AT neurotica DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1506281932040 DOT 6924 AT igor2priv>
	<DUB125-W14CCFC72BE0E267D38C8EEC6AB0 AT phx DOT gbl>
	<20150630192013 DOT 552208038A28 AT turkos DOT aspodata DOT se>
	<CAM2RGhR4LKmT7ko19fU_j_ThkqjmiHGNDLsvE+HrVqCYj=ANdQ AT mail DOT gmail DOT com>
Date:	Tue, 30 Jun 2015 16:11:41 -0400
Message-ID:	<CAM2RGhRuw-NCQ4K3pG0FrdOFsnUDqbwCJeTzTDSN7A=NgHuW5Q@mail.gmail.com>
Subject:	Re: [geda-user] gEDA/gschem still alive?
From:	"Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t5UKBk7K003066
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

Karl, I think a lot of people might have tuned out of this thread. You
might find it more viable to repost what you just said on a fresh one.
It looks interesting.

On Tue, Jun 30, 2015 at 4:09 PM, Evan Foss <evanfoss AT gmail DOT com> wrote:
> Dave McGuire : I have no hardware in orbit. I have however been
> tinkering with electronics since age 4. I have a BS and I have been
> working in a research lab full of phd's and professors for 6 years.
> Point being that while I am a lightweight went it comes to
> professional design but I am well acclimated to egotism and
> condescension. I don't think that is what John is doing here.
>
> I don't tend to use John's stuff but I did try to contribute a few
> years back to PCB. Then as now it was low coherency. Since then it has
> gained doxygen documentation which makes things marginally better. I
> still feel that too an extent the developers created something no
> outside contributor could manage to add to with out a very steep
> learning curve.
>
> On Tue, Jun 30, 2015 at 3:20 PM,  <karl AT aspodata DOT se> wrote:
>> Hannu:
>> ...
>>> One thing is missing. Draw schematics. -> convert to symbol and use
>>> as block.  Doing schematics nicely in hierarchical way is still a
>>> lot of hand work.
>> ...
>>
>> I have a program
>>
>>  http://turkos.aspodata.se/git/openhw/pdftosym/pintosym.pl
>>
>> that lets you create sym/src-sch file sets.
>>
>> In http://turkos.aspodata.se/git/openhw/pdftosym/examples.pintosym/
>> I have some examples of its use.
>>
>> For hierarchical examples see 1wire_driver.* and hier.*
>> Another example is http://turkos.aspodata.se/git/openhw/regulator/include/
>>
>> If you have a schematic containing something you want to move to a
>> subschematic:
>>
>> . define a .pins file cont. the needed io's
>> . run the program
>> . refresh the library browser in gschem
>> . include the newly created .sym file
>> . mark the things you want moved to the subsheet
>> . edit-cut
>> . mark the newly inserted symbol
>> . hier-down
>> . in the new subsheet, do edit-paste
>> . connects nets to the right io-symbols/pins
>>
>> Caveats:
>>  pintosym.pl lets you define what kind of type or label a pin has,
>>  see hier.pins for an example, but to do so you need to define the
>>  mapping
>>
>>  the program was designed for mcu-kind of components, something with
>>  lots of pins, and if you only have a few pins, the pin placement is
>>  somewhat awkward
>>
>> To see the program docs: pod2text pintosym.pl | less
>>
>> Regards,
>> /Karl Hammar
>>
>> -----------------------------------------------------------------------
>> Aspö Data
>> Lilla Aspö 148
>> S-742 94 Östhammar
>> Sweden
>> +46 173 140 57
>>
>>
>
>
>
> --
> Home
> http://evanfoss.googlepages.com/
> Work
> http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/



-- 
Home
http://evanfoss.googlepages.com/
Work
http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/

- Raw text -