X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Virus-Scanned: Debian amavisd-new at papyrus.altaweb.hu Date: Sun, 13 Sep 2015 19:01:32 +0200 From: "Lev (leventelist 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: <20150913190132.1926c471@jive.levalinux.org> In-Reply-To: References: <20150913140631 DOT 1da1b78d AT jive DOT levalinux DOT org> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; amd64-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id t8DH1fjb021144 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, 13 Sep 2015 08:43:01 -0800 "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" wrote: > 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? Instead of fire up gvim, you fire up sqlitebrowser. One of my goal is to avoid manual file hacking. But you still can do it if you like. A script still can manipulate the file. I don't think xml/yaml is a better choice. They get very, very ugly. I don't see any reason why not use SQLite. Lev -- 73 de HA5OGL Op.: Levente