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:date:message-id:subject:from:to:content-type;
	bh=73MGzu5B562CPlepep2ruKLLfh+lWeVRi5ITrK3tmcQ=;
	b=wSMWwGzGk4QnkW7X6kVaKLq9Dk4YlJjjKagMbSvY5ZTD5tq3pDZ3zQJTvFkDDDw9HU
	G0GKImuZm28bsJGFS7wrJy7qo5xMmfTZ1GPcUxNCOmTfipD5hBjL6unvNO0tDAIQm0Lx
	Td9s6o3gz6tzsYARZBr1TH7NKiDo7EolIpnoL9jd3HVsIQs0A3ta5MLZzF9Qu8/2K4Xw
	SU1XrkkINNBd87zh9NDSW0V5WzxEYf2pTGMMUnOgcr98j1qP85xKpQsxYsE53rgfAmjw
	8pnYbQQtmLd7Gi8Kn8Tlz5v/lkjDCklE3jmXclW7guWMrkFzyOljSsef3Z+EnwsTbM6/
	otDQ==
MIME-Version:	1.0
X-Received:	by 10.194.89.5 with SMTP id bk5mr54438274wjb.144.1440539915713;
	Tue, 25 Aug 2015 14:58:35 -0700 (PDT)
Date:	Tue, 25 Aug 2015 13:58:33 -0800
Message-ID:	<CAC4O8c_PFbZFYfBfw0cQwG9CDtrOxqxSEPunMQy7U3ueN7K1_Q@mail.gmail.com>
Subject:	[geda-user] SQL PCB file format
From:	"Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Reply-To:	geda-user AT delorie DOT com

On Tue, Aug 25, 2015 at 1:02 PM, Evan Foss (evanfoss AT gmail DOT com) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> On Tue, Aug 25, 2015 at 4:37 PM, Peter Stuge (peter AT stuge DOT se) [via
> geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>> Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
>>> The problem that has been consuming my mind or a few months now is
>>> how all of this should be represented in memory.
>>
>> Linked lists. The overhead is small.
>
> Yes but you want the lists to be meaningful. Just having a list of
> elements on a layer is not enough. The way you store the info makes
> moving footprints or moving traces more straight forward to implement.

Igor is already moving things from script:

   http://repo.hu/projects/pcb-rnd/gpmi/rosetta/30_move/index.html

I also really wish file format's could keep on being text.
Internal SQL sure but I don't see the point of a not-human-readable
format.  Its not
as if the size or parsing time is likely to be significant.

Now I'm going back to my strategy of not caring what happens to gEDA
and just using my existing version.

Britton

- Raw text -