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=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=HTemRjDyLVVPd0IjNoj+YXOp5xhrTPpP7vDe/Gcg9A4=; b=kCRP4puwNjOyg5EotuSsbps9Kv3EkE78BHTBo7//BwkSFO9ABkrYcFum+v+yoXUQkN 2WCB39q5YXRWf5J3UydpPcE6pVufDCLGNtWk7G7LHiijYaZ+hauI2k5H+4Mmme5tZEij GpmfrElSJ8waBbbRAP0jyLO71v4VinsPz0tR+6bJG6HJGsQha5nr0iYoi0UXLcPhB/Id l/qvwyqc6GQqxM1AT9m9oCoJKKG3uA23ACgvs4A92LgSCPOdHpT/w7CuA0uuzmcc+Glu cVfyuKoxnbESLOFn52famvEmVyhjmDeBEuKUWEbihpZL5t894VF6By7RPFpID6CFm7/B Picw== X-Received: by 10.194.104.39 with SMTP id gb7mr17978213wjb.150.1442151596434; Sun, 13 Sep 2015 06:39:56 -0700 (PDT) Date: Sun, 13 Sep 2015 15:39:54 +0200 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] Apollon Message-Id: <20150913153954.f9010800568c28a6805c86d2@gmail.com> In-Reply-To: <20150913140631.1da1b78d@jive.levalinux.org> References: <20150913140631 DOT 1da1b78d AT jive DOT levalinux DOT org> X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 The name padstack have already been used before by commercial company. In case this is a problem it could be better to define a pin object which is an electrical connection point. I guess a footprint and pin essentialy could be the same type of object although a footprint usually have several pin objects. It would probably be enouhg to add possibility to group objects as pins so they could be found and manipulated. Grouping may be achieved both with attached attribute or put into separate sections for each pin. "refdes.footprint.pin" ? > I finished the documentation of my proposed data structure. I pushed it > into the home/lev/apollon branch. There are slight changes from the > former version. > > Please give me feedback. This is my first push into the repository, so I'm > also open to comments about usual commit messages, etc. > > I also attach a pdf of my document. > > The next step is to make a decision on data structure, and how to implement > that in gEDA/pcb.