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=20210112; t=1679229528;
	h=mime-version:message-id:in-reply-to:date:subject:to:user-agent
	:references:from:from:to:cc:subject:date:message-id:reply-to;
	bh=GKZQjZU2WY31Npn0vAkV8pKn056MEviSWwb612rY9K0=;
	b=NguObxK9J78fT3sOuwi/IXVgy7fgCiWjPPMAWe8v9rTnICJiWk/RZZhLThOwUTX9Zi
	ot20O/92iXb8hAi3cZNSP4F13+jwHYP/3rb4cycHkE2/pATrOwqeGHuE7kH+/iAtNrag
	G0w5Ge03pkXF2im1+OWEOg+dD8keAi1TAuccEhrQUqXPjcBqQSm/VYUQxdpW/oUY0rag
	SFAr7daxb8gDnm4dbp61G7kO/2XYX4ZQW63BCDIa70h9i858mYzzN5/Y30pFXUOx4OLI
	28dsoRvyyfewledU2fQSI5rVGAcnDUwPdvk4iSxuIjplsl2naUuJgWFPxd9HzkRBIk7u
	gSsQ==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20210112; t=1679229528;
	h=mime-version:message-id:in-reply-to:date:subject:to:user-agent
	:references:from:x-gm-message-state:from:to:cc:subject:date
	:message-id:reply-to;
	bh=GKZQjZU2WY31Npn0vAkV8pKn056MEviSWwb612rY9K0=;
	b=bmz2tiIrayT2PiRKeWogUBz1F7Ta2rCRwoO3wHpOLl5wNcQCdUG2fheqmOVRK8rrEC
	b0JLUT1Xp6iEEKP95egSpPQSpHAWiwRg/F3trd4K7+k6utsrGX/nPF/24p/BW64gwQEm
	w2lwhzW8+ozUQxPAb6mNDtFKOEj2Agdbz+rD1Zmc/b04wSG2V/ACGLP9PbHdApcNoMDw
	/3Tgg1x364m7pF243csjVhkdIJ/Ur3de+S/NCgHKMHr2Z2+h6xLKt4Y1nE6je0VtFvWY
	CAhsssMoUlQtlUR+DU7vEWkDFMUkocd9MPRN6zghzS/aQ5Go8EwqZmc07fINLB8hKtW+
	Wm4w==
X-Gm-Message-State:	AO0yUKWG+y1Du06VT6iK/fvlbfe+yH0J4q1lfIoisn5Cvx5yMonIQXWl
	i6WGyKitoZ18Ydse3WGKM0pcCrNMRW4=
X-Google-Smtp-Source:	AK7set/YH8stGpu9RrQhPu+5F8iVn2qp+H7TboFtK1SyBJDO2UrOm3LcSLxcSBmHrolznPJpMBEcCQ==
X-Received:	by 2002:ac2:57db:0:b0:4dc:8215:5531 with SMTP id k27-20020ac257db000000b004dc82155531mr5464705lfo.6.1679229527183;
	Sun, 19 Mar 2023 05:38:47 -0700 (PDT)
From:	"vzh (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
X-Google-Original-From:	vzh <vzh AT lepton>
References:	<20230314184208 DOT 7302885F61C5 AT turkos DOT aspodata DOT se>
	<87y1nvz5s0 DOT fsf AT lepton DOT mail-host-address-is-not-set>
	<20230317183608 DOT 91AEC85F61C8 AT turkos DOT aspodata DOT se>
	<87ttyjyvnr DOT fsf AT lepton DOT mail-host-address-is-not-set>
	<20230318083329 DOT E1B7885F61C8 AT turkos DOT aspodata DOT se>
User-agent:	mu4e 1.8.11; emacs 28.2
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] tools for sub pcbs
Date:	Sun, 19 Mar 2023 14:15:48 +0300
In-reply-to:	<20230318083329.E1B7885F61C8@turkos.aspodata.se>
Message-ID:	<87wn3c9aqy.fsf@lepton.mail-host-address-is-not-set>
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

Karl,

"karl AT aspodata DOT se [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> writes:

> Why not laeve sch2pcb as is and develop the scheme version instead,
> perhaps we could call it lepton-2pcb (lepton implies sch so that is 
> redundant) or have it as a menu item in the schematic prg. ?

It is about code base reduction while attempting to not lose any useful
functionality and getting feedback from the users of lepton.  Previous
version of gsch2pcb is always available in geda-gaf.

> I can do testing and possible some scheme but I'm not fluid in scheme,
> just tell me what to do.

Do not hesitate to ask me anything about lepton code, even off-list if
you want.

What you can do:
- Opt a related pull request at https://github.com/lepton-eda/lepton-eda/pulls
  (e.g. https://github.com/lepton-eda/lepton-eda/pull/1008).
- Check out the branch and compile it on your system.
- Report any errors.
- Try if the program does TRT on your projects.
- Look through the code if you want, we can discuss and amend changes in
  any commit.
- Suggest any changes, comments, new tests or what can be tested better, etc.

> From what I have guessed, my goal, the program should do:
> . read lepton and pcb configs to find the libs.
>  Unfortunately pcb has three config files:  pcbrc preferences  settings,
>  which one has the final say about libs ?
>
> . read the sch file, find refdes and fp or refdes and source attributes
> . do a netlist as usual
>
> . find the footprint file[s]
> . find the source file[s]
>
> Unfortunately neither sch and pcb file formats resolve the
> issue of files with the same name in different directories.

It's a different issue.  I keep it in mind though cannot work on it yet.


>
> . put all fp's in the *.new.pcb file as usual
> . get the source files pcb sibling, adj. refdes (add the source files 
>   refdes) and save it in the same dir as the orig. sch file
>
> and then possible:
>
> . remove not used fp in the target pcb file
> . write out a nice message to the user
>
> or tell pcb that
> . there is fp's remove
> . there is fp's to add
> . there is subpcbs to add
>
> ///
>
> An extension to the last part, is that pcb could tell lepton to
> . change an attribute of a symbol
> . change some connections
>
> ///
>
> All the above goes for pcb-rnd also if possible.

I cannot but agree with all the above.  Our approach is just doing
reliable changes on each step trying to avoid stressing our users :-) It
includes many tests and mandatory review of all production code.  I
don't plan to rewrite anything at once, it would be error-prone as the
code base is very big.

With best regards,
  Vladimir

- Raw text -