X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com 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=76tuqDMSYBp6mOAgEeHTZzrMWm+YaewzNfJr8L4Wak0=; b=xrgXovT59Mv262pTAyK+TpijM6AwOf0rdzMCHn1R/ie/1dliN7L3tB0MsEX3KZPp7T ZypfEnesrKouUvR1pNN4sy4mgcVVl/qu40/R4Gs/H29a1Vx7JZSXFp2wBhW2X8nR4sLy PkRQVoT4k2//TCeD99/yjUqoKUgiOm2hz+3K94pKdOzkmWfValCTh9QEQdqQGVqc8G9t 43T7BllgxSRXWcCBov3UnC+KRpC+i32fw/IyUbDWOZHmjCxym29MO4nrIQbzIrxk9Jb1 6cNjvySXKU0DxQTs/Ppi9IN45iHKtBZ+hmOilWneapuxAenmYAzMc6o5qNw1lE9oWZ0t Xssg== MIME-Version: 1.0 X-Received: by 10.202.222.213 with SMTP id v204mr16523949oig.103.1426618391028; Tue, 17 Mar 2015 11:53:11 -0700 (PDT) In-Reply-To: <20150317182617.22729.qmail@stuge.se> References: <CAHLh21Cdm=YZuqCQ+gCHSviJquahr6cnAQ-VBLR4BSs-nfHOig AT mail DOT gmail DOT com> <CAOFvGD4+4bHXNYLvePi70wb_1A4=dQgb_Ov3xBghoKbXQUsSGA AT mail DOT gmail DOT com> <5508413E DOT 4000405 AT ecosensory DOT com> <C2997FC5-EE8B-47E4-A8D5-24B6D22B2D64 AT noqsi DOT com> <20150317182617 DOT 22729 DOT qmail AT stuge DOT se> Date: Tue, 17 Mar 2015 14:53:10 -0400 Message-ID: <CAOFvGD7vgcVoHw6OeE98iA60755n8gbs6jbtv56O5+AcqWM1vQ@mail.gmail.com> Subject: Re: [geda-user] pcb alternatives From: Jason White <whitewaterssoftwareinfo AT gmail DOT com> To: geda-user AT delorie DOT com Content-Type: text/plain; charset=UTF-8 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 On Tue, Mar 17, 2015 at 2:26 PM, Peter Stuge <peter AT stuge DOT se> wrote: > ... > Which elementary objects would you use instead of the current > predefined ones, and what would be a couple of concrete advantages? I know I am not John, who the question was directed at. However, what would be beneficial to the organization of information in PCB is the addition of (and use of!) a generic (and I stress generic!) grouping element. This element would have the following features: (1) to contain graphical primitives (2) to contain other groups which may in turn contain other groups or graphical primitives. Without the ability to cleanly deal with things such as sub-layouts, panelized designs, and multi-layer footprints is greatly diminished. The burden of this is passed onto the user who must try to compensate, somehow... -- Jason White