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=20161025;
	h=from:date:to:subject:message-id:mail-followup-to:references
	:mime-version:content-disposition:in-reply-to;
	bh=gyAoZBj7wDu3GFm/gO956fcKO3IngjwXtpyfFyePr78=;
	b=irV8566cIcrRH7if+UJRoCffteJfzzoNGlrYBK0+VdBkeaCWGNCw8EcSbrDdErOziB
	OMipVwqnXzeFXkHDlQPdXp15dCdGhKcMtTcrEvsIcOqadlL2WV8KRF4f6BAQlRPTnA8i
	DHJsP4zHF11wcpA/TTexy9K0zJJMzO6gK2iiOfzllJrpRPwIYaJ2SzdZRs8Juiugp5yf
	yLxNEGQf8E2xbPWRmlFTPNMqbLEpO+bCQpL/5NIipopKzvo5xfCXBMrlV7Lcimdhy2Lk
	w6l+3x486WOU7V7Q+4f+kP5ALxziuDZyPE6f1DPtUwEv2wAQ4m/ESdRnrfKgv8UDBRj/
	p95A==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:from:date:to:subject:message-id:mail-followup-to
	:references:mime-version:content-disposition:in-reply-to;
	bh=gyAoZBj7wDu3GFm/gO956fcKO3IngjwXtpyfFyePr78=;
	b=uZGnZZmJ4/dnnn9pWPFscRG07FLhTXbj1QPgWaHa9MegoTWX5tfUIyGNtjy7R8aRCK
	YzmOYkndeF58of++0U2iltP3Gq7XHpuWfMn9iYISEpVC+I1QHasbGSHtRDSXpxq/sobc
	suj8TB8Dm1/S1/NsN+Ow1I2zRCxesfoweGxMBsECyUjJpwFcolpxodBPKhKrkmpapuTJ
	K8RhV89TUKIlru6ahTywhH7WHYU88M+bEuooHmPB5xhwUMoq8JgKYTGZYzbqogJupFku
	OlOp3/sPe33G4nZFiGs7x3D5FFD2Xt6F6ETy7FPaHcLKCLqHSM7X6tRbb3v9e8XTNH91
	zaYw==
X-Gm-Message-State:	AOAM532WqnSY/paxnOh/GqHm0Ojc4PoeXyzLdUL57xTFb/bTsG3Q+0PU
	nAokLAf0VllS9OJIMveiUQIvw5aqh5c=
X-Google-Smtp-Source:	ABdhPJw09A8uoqvKuM+NdlMX6t1agSFpvKT+yudrXpt+QXJb5VQ8V7Q9n8b5BbL0D3lab3diDgQ2cQ==
X-Received:	by 2002:a19:ca13:: with SMTP id a19mr22690371lfg.647.1625731667456;
	Thu, 08 Jul 2021 01:07:47 -0700 (PDT)
From:	"Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
X-Google-Original-From:	Vladimir Zhbanov <vzh AT lepton>
Date:	Thu, 8 Jul 2021 11:07:45 +0300
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Thank you - some requests and an offer
Message-ID:	<YOayUYFK9b1GiBoB@lepton>
Mail-Followup-To:	geda-user AT delorie DOT com
References:	<20210707101437 DOT 2c7c63a6 AT queeg>
MIME-Version:	1.0
In-Reply-To:	<20210707101437.2c7c63a6@queeg>
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

Hi Stephen,

On Wed, Jul 07, 2021 at 10:14:37AM -0400, Stephen C. Menasian (menasian AT ptd DOT net) [via geda-user AT delorie DOT com] wrote:
> Thank you very much for reviving the gEDA project. gschem has been my
> schematic capture program of choice since it was in the beta stage. When
> support seemed to have vanished a while ago, I continued to use my old
> (locally compiled) version. The substitute offered by Fedora (Kicad, I
> think) was not to my liking and there seemed to be no tools to port all
> my gschem schematic and symbol files to the Kicad platform. When I found
> that gschem support was revived, I was overjoyed.

First (-an advertisement-) a couple of words about gEDA and
Lepton, our project.

I started working on gEDA in 2009.  Since about 2011 I realized
that the project dies and tried to get it alive as I could.  In
about 2014 (cannot remember) I released geda-gaf 1.9.2.  It was
the time when nobody wanted to do such a work.  In late 2016 we
forked and now our fork project is named Lepton EDA.  I don't want
to start flaming wars here so if you desire, you could google
about what happened at that time.  For me, the biggest issue was
introducing xorn (and its dependency python2) into the project,
which effectively hid my work on legacy gnetlist of that time.  In
Lepton, we're still trying to support as many distribution we can
and keep gEDA alive.

For example, here:

https://graahnul-grom.github.io/

you can see that there are several Lepton packages, the list
includes Fedora rpm as well.  (There is also a Lepton wiki page
about other supported distributions.)

> 
> Now to my requests. I apologize if these requests are already somewhere
> in the mailing list; I haven't gone through all the past postings. 
> 
> 1) The old gschem had an option in the print dialog to print the visible
> region of the schematic. I used this frequently for several reasons - for
> example, to have an uncluttered large scale print of a part of the
> schematic while developing a circuit. This option is missing in the
> present release; it would be nice to have it back. My current workaround
> is cumbersome. I export to pdf with the highest possible resolution, open
> the pdf in GIMP, crop and scale it and print the result.

Probably just nobody remembers :-) or gschem went other way since
the fork, but in lepton-schematic (the lepton analog of gschem) it
can be easily done by using File->Image and choosing PDF as the
output format.  Just what you wanted, just the visible part of the
canvas will be output.

> 
> 2) The old gschem behaved thusly when a part (or portion of a circuit)
> was selected and copied (at least the way I had set up my gschemrc):
> The selection remained with the originally selected part(s) after the
> copy and the new copy was not selected. The new gschem transfers the
> selection to the copy when it is placed. It would be nice to have a
> gschemrc option to allow the selection to remain with the original part.

lepton-schematic behaves just like you described the old gschem
did.  If you want the behaviour of the "new" gschem, you can still
have it.  It's easily done with lepton with a little extension by
Dmitry (dmn):

https://graahnul-grom.github.io/scm/shift-sel-to-pasted.scm.html

See the comments there.


> Finally, an offer. I have written a C program which I call "geda_parts".
> It reads a .sch file and creates an almost publishable parts list. For
> example: "geda_parts xxyy.sch R" would produce a file "xxyy_R.parts"
> which lists all the resistors in numerical order. This file is also useful
> for finding duplicated reference designators and holes in the reference
> designator sequence. It currently works for most of the common part types
> (resistors, capacitors, transistors, ICs, inductors, etc,). I have yet to
> make some modifications to handle multislot ICs and will probably do some
> more cleaning up but, if there is any interest, I can post the source
> once it is stable. 

The work had been already done in legacy gnetlist just before
replacing it with gnetlist2/xorn so nobody might notice it.  In
lepton it is just here.  There are three simple backends:
partslist1, partslist2, and partslist3:

https://github.com/lepton-eda/lepton-eda/blob/master/utils/netlist/scheme/backend/gnet-partslist1.scm
https://github.com/lepton-eda/lepton-eda/blob/master/utils/netlist/scheme/backend/gnet-partslist2.scm
https://github.com/lepton-eda/lepton-eda/blob/master/utils/netlist/scheme/backend/gnet-partslist3.scm

Simple enough, eh?  And easy to forge your own one from the
examples and run, if you wish, with just `lepton-netlist -f
backend-filename ...'.  IIRC, I even posted a simple example on
the list on how to easily format latex output a few years ago.

Really, nowadays any lepton backend sorts its output, but
partslist backends allow you to adapt sorting of the parts for
your taste.

If you mean something other/bigger/better, please let us know,
just publish your program somewhere or file a bug report on Lepton
site here:

https://github.com/lepton-eda/lepton-eda/issues

HTH,

-- 
  Vladimir

- Raw text -