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=69xmUdGiW7wnZiW04p7c1eS+7nwhnjCQSMwn4leHHbE=; b=D3mIBZpZP4vAyj1NUpuJeLuUkd24bGXnRwYRjZRA/rOUt751fdsWeWdgY1SFSZGX+U XlPtjfFv16wtNWcnPORV0wY00GEnM2KbSbr91vGsWwyqTc1AmyVwwTYRDKYFWwVcEh9q 83ySBqxhaPtPDk2FYWpYQ82kDhTO7/L36Bo2OEKONOcSMvjIVHsxwn+k+vBOGsmUEPov kLExEmXEns6SawRKBCvKGVOUEUF1R3lMq5QEfrjGohnVFpX1WXMJJ5MfCGFaZsamnD17 wMNDUhBDBpHISp9k4SRZvmNBgXy1hW/XweExwCQRShotdRRLis7vsKyoTfGB4L4t83kK +Bmw== MIME-Version: 1.0 X-Received: by 10.107.138.216 with SMTP id c85mr22290694ioj.187.1440495914311; Tue, 25 Aug 2015 02:45:14 -0700 (PDT) In-Reply-To: <55DC31E0.9050606@jump-ing.de> References: <20150824223846 DOT 0ba61ba7 AT jive DOT levalinux DOT org> <55DBA2B7 DOT 1080501 AT ecosensory DOT com> <55DC31E0 DOT 9050606 AT jump-ing DOT de> Date: Tue, 25 Aug 2015 11:45:14 +0200 Message-ID: Subject: Re: [geda-user] pcb file format From: "Levente (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com]" To: gEDA User Mailing List Content-Type: multipart/alternative; boundary=001a113ecc1645e7d8051e1f97da 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 --001a113ecc1645e7d8051e1f97da Content-Type: text/plain; charset=UTF-8 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] 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/ > --001a113ecc1645e7d8051e1f97da Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Markus,


I know this. = If we change the file format, we have to rewrite the scripts anyways. SQLit= e 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 rep= ort 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 ma= chine.

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 d= e) [via geda-user AT delorie DOT com<= /a>] <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. Thi= nk of the thousands of tools out there which act on layouts independently f= rom 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 d= esigns. Having a text file format, along with importer and exporter, the ne= ed 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.<= br>
Sounds good!


Markus

--
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. (FH) Markus Hitter
ht= tp://www.jump-ing.de/

--001a113ecc1645e7d8051e1f97da--