X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Thu, 29 Jun 2017 21:17:23 +0200 (CEST) X-X-Sender: igor2 AT igor2priv To: geda-user AT delorie DOT com X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu" From: gedau AT igor2 DOT repo DOT hu Subject: [geda-user] [pcb-rnd] Subcircuit example: reusable board outline + mounting holes + details on the code cleanup Message-ID: User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Reply-To: geda-user AT delorie DOT com Hi all, the following video demonstrates how to use subcircuits to specify the outline and mounting holes of a board: https://archive.org/details/subc-box2 The subcircuit can be then reused easily for fitting other boards in the same box. Testing is welcome! A summary about the technical details at the current standing after 4 weeks of development: http://repo.hu/projects/pcb-rnd/devlog/20170629_subc.html Other than such practical uses, implementing subcircuit is also a major cleanup in the code base. After the layer concept/code cleanup, this is the second part of the long awaited "clean up the internal data structures" effort, turning our flat-data-with-special-cases into a generic tree. (Later on this will include removing special cases, when elements will be removed in favor of subcircuits, which is just a generic way of grouping arbitrary objects.) Roadmap: the remaining time in this development cycle will be used for IO plugin coding and generic bug fixes. My current plan is that subcircuits will get pin/pad capabilities in the next cycle, which will make them a capable replacement for elements/footprints, but elements co-existing; then in a 3rd cycle I would remove elements, element-lines, element-arcs, pins and pads (with all the special-case code). This should e all be finished this year. Regards, Igor2