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=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=fWToNzjKM44KspgyVJ1vGXfyWYMFvkZVlAknZmOqa5Y=; b=aCqy6AZ2t7zVuTIN9Yf03PfoVE2uLo3ZS3C8vC5zrkUJrc6nHnB3fTp7855lLkOUtg c0AyJgBa1IlJbksuSVDnObnAMw+XoZ0LQ8/TwJBQ6YUQml/QFxNenuvN6RpsDvhy6I8m J4IGgN/jkYz0MVTrTD47YCwZawlSgArvbk0Zt7KXt4fpx374cnjmUfxt0Hvud9bEqkTi wLbMOJnCE4QvfHfPa7PDBsLylvmyC1UgJ47i65fbOVxDwZXr+2RpBoFLUeEDiaC+a35t 1d8wrpWNsWJsmX0R6a64Ui0kT19fssDJtCfaNWP3xtmhkJEYmUPMc0UOMEBjCH50AWUO D7SQ== MIME-Version: 1.0 X-Received: by 10.194.109.97 with SMTP id hr1mr19353175wjb.38.1442162582038; Sun, 13 Sep 2015 09:43:02 -0700 (PDT) In-Reply-To: <20150913140631.1da1b78d@jive.levalinux.org> References: <20150913140631 DOT 1da1b78d AT jive DOT levalinux DOT org> Date: Sun, 13 Sep 2015 08:43:01 -0800 Message-ID: Subject: Re: [geda-user] Apollon From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie 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 Sun, Sep 13, 2015 at 4:06 AM, Lev (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > 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. I suggest putting it in the file as something human-readable. It's an easy translate to SQL. SQL is unlikely to be a popular choice for people who don't already use it, and all you get for it is a little more speed from the parser. I think there are lots of users who just want to e.g. change a selected "R1" to "S1/R1" (that's how I started anyway) and they are unlikely to want to fire up an SQL interface to do it. Why make them?