delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2016/04/01/06:44:20

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <1459507382.2911.311.camel@linetec>
Subject: Re: [geda-user] PNG export question
From: "Richard Rasker (rasker AT linetec DOT nl) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Date: Fri, 01 Apr 2016 12:43:02 +0200
In-Reply-To: <201603232056.u2NKuuGr023019@envy.delorie.com>
References: <1458766246 DOT 2911 DOT 85 DOT camel AT linetec>
<201603232056 DOT u2NKuuGr023019 AT envy DOT delorie DOT com>
Organization: Linetec
X-Mailer: Evolution 3.10.4-0ubuntu2
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

DJ Delorie schreef op wo 23-03-2016 om 16:56 [-0400]:
> The easiest way to do custom outputs like this is to post-process the
> *.pcb file to a new file, and print that (just grepping out all the
> line/arc/via entries, for example).  For example, I have a pcb2paste
> script that extracts all the pads and edits them (attached).
> Otherwise, drawing pins and pads is handled differently for the GUI
> than for the exporters.

Hello,

I'm perhaps a bit late with my reply (been exceedingly busy), but thanks
for your explanation.
Yes, I thought of something like this, but didn't have the time to
really get hands-on with this.
I think your Perl script is a nice starting point for what I want -- the
only thing I have to do is just learn Perl ;-) Nah, it seems simple
enough, so I think I'll go do some hacking in the next few days.



BTW, I made some simple Bash helper scripts of my own for PCB projects
that people may find useful (some of these I already offered before, but
I updated & improved them somewhat), see
http://www.linetec.nl/electronics/downloads

pcbcreate: generates a PCB + gschem project, based on gschem and PCB
template files. It sets the correct path attributes in PCB for importing
the associated gschem file; also, the project name is set in gschem's
title block, as well as on PCB's silk screen layer.

pcbzip: generates one zip file containing the exported Gerber files, as
commonly accepted by manufacturers. With the -xy switch, the .xy
and .bom files are also generated (the former included in the zip file,
the latter separate). The .bom file is sorted with bomsort (see below).
If the project name is omitted, pcbzip lists all PCB files found in the
current directory and asks which one should be processed.
The separate Gerber files are deleted after inclusion in the zip file,
as I found that I very rarely need those files. Deletion hugely reduces
clutter in the project directory.

bomsort: sorts the exported .bom file, with lines sorted in alphabetical
order according to refdes type (C, Q, R, U etcetera), and refdes'es
within each line sorted in ascending numerical order.

template.sch and template.pcb: gschem and PCB template files

I'm still thinking about a crude versioning tool as well -- I found that
the more complex projects take at least two or three iterations before
the final design is satisfactory. So perhaps another tool to create a
copy of a particular project with an updated name/version number might
be handy as well (at the moment, gschem and PCB file names and
attributes must be changed manually at such an occasion).

Comments and ideas are welcome, as the existing scripts can no doubt be
improved.

Anyway, thanks again,

Best regards,

Richard Rasker


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019