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=qdHUYwaSgU7FSxJ/cD0b97O9bAyR4x/Q/AWIY3fBiBQ=;
	b=Rif2NWlcdgIsG7nYaWQAkfP7i5DZaFGljyHMShsuwCzop9BfXHBVY/vyuIjqrGPIit
	H6dUn771ZbsDGIA3RaTqdISfPjLCuPsmG1pBAwRaPZ9hFPJJeH1kvy6EjVnSzWk+ZTUS
	+xb2TssMNJgw+lLaBEk9MQNXeN/svX5i+BmmFSDK8deE/1hJpnLfl4l+e4sSFNs3vwS6
	7ko/cD1oAKFFxdFhto+R8M6Rt58tzrITAV5z8kXtMFfB8wBjmoHqNxTqq5+9VvyWksX/
	7ry+Kgl4QD5JXQoHRbd5yGSKmOwy9HYHq80lari4bHO6ZyBlkI9qACU+DKzdL/biO/dr
	S9GA==
X-Received:	by 10.152.30.73 with SMTP id q9mr25355469lah.31.1440497680347;
	Tue, 25 Aug 2015 03:14:40 -0700 (PDT)
Date:	Tue, 25 Aug 2015 12:14:38 +0200
From:	"Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] pcb file format
Message-Id:	<20150825121438.f3509b62247d6d2a6c0bc2d7@gmail.com>
In-Reply-To:	<CACwWb3CYGx9hyTB5T-v=oCZd=Vs2VAGQ65h9vWhugt2COuVHUQ@mail.gmail.com>
References:	<20150824223846 DOT 0ba61ba7 AT jive DOT levalinux DOT org>
	<55DBA2B7 DOT 1080501 AT ecosensory DOT com>
	<CAHUm0tNAY8TY485-imFoTHJqRha=99bmO_3a9f_jjpWCU4x8Zg AT mail DOT gmail DOT com>
	<CACwWb3COWw41-L8dNw9qhfkYT2wF7=7oC1cEhRbKLV4pHdTMaA AT mail DOT gmail DOT com>
	<55DC31E0 DOT 9050606 AT jump-ing DOT de>
	<CACwWb3CYGx9hyTB5T-v=oCZd=Vs2VAGQ65h9vWhugt2COuVHUQ AT mail DOT gmail DOT com>
X-Mailer:	Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version:	1.0
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

You might be correct. I guess it could be figured out like this:
  1. Write a list of which operations PCB can do on the file while editing.
  2. Figure out if SQL will do these operations efficiently.

I guess a very common operation is to change footprint coordinates or rotation. A more unusual which is allowed to use more time would be to search the coordinates in sorted order and renumber the components. Then drawing the rats nest either nets are searched for connected pins or pins are searched for connections.




On Tue, 25 Aug 2015 11:45:14 +0200
"Levente (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> wrote:

> Markus,
> 
> 
> I know this. If we change the file format, we have to rewrite the scripts
> anyways. SQLite has a bindings for all scripting languages. Perl, python,
> LUA... you name it.
> 
> Think of that your scripts will be much more compact. No need to implement
> parsing N times.
> 
> Generating a drill report is just one query of the database. Your script is
> just to pretty print the output.
> Same goes for XY files for your pick and place machine.
> 
> No, I DON'T want to start another flame war. We had enough in this list. I
> write code.
> 
> Lev
> 
> On Tue, Aug 25, 2015 at 11:14 AM, Markus Hitter (mah AT jump-ing DOT de) [via
> geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> 
> > Am 25.08.2015 um 10:31 schrieb Levente (leventelist AT gmail DOT com) [via
> > geda-user AT delorie DOT com]:
> > > As I stated, text is not yet supported, but will be added to the
> > > specification.
> >
> > Maybe you should concentrate on this, first, to gain acceptance. Think of
> > the thousands of tools out there which act on layouts independently from
> > pcb. When the text file format goes away, they all have to be rewritten
> > pretty much from scratch. No more AWK, shell scripts or similar to do this
> > tweak or another.
> >
> > You have to at least write an text importer anyways, for all the existing
> > designs. Having a text file format, along with importer and exporter, the
> > need for a binary file format pretty much vanishes. Handling all the
> > objects internally with a database library is perfectly fine, IMHO.
> >
> > > vias are specified as padstacks. You can define any pad on any layer.
> >
> > Sounds good!
> >
> >
> > Markus
> >
> > --
> > - - - - - - - - - - - - - - - - - - -
> > Dipl. Ing. (FH) Markus Hitter
> > http://www.jump-ing.de/
> >

- Raw text -