www.delorie.com/archives/browse.cgi | search |
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=HQ0qJZ0uOAy2gPFQYecY75KLRCzrd4RplRGcW7EKMHc=; | |
b=BnuBUrKmx62cViTsiToM2ngpCgBRh018jxGSRnbb+bZUsiNSqf+JpbptcHCbRJgRdc | |
9Mr9mI1wfthlm5gXldJIdMqtePcQy+rsVjlkPL03CByQbrr3JqKNnqz0VHwgZto3iuOE | |
ERDUzWqtWdx4gcqrGYYcdAG73nRZ3jtvdYwb9gpKS0RWPp4uIOCXF5q5m8uC0ox664yL | |
FTh/tKArEjB6rYQjat6gVTY1pBrTF0YnKRuc33Vgvd7LirT0OoErNS+c+a9rEuPmapec | |
lMEzUuhp8x+E6NVEG7bFAa4ZyLS2cg1GPzEcrx9igJqNZKPxiVIppz3cCEnfPAwMg756 | |
YC0Q== | |
MIME-Version: | 1.0 |
X-Received: | by 10.180.85.104 with SMTP id g8mr2180611wiz.57.1442024964801; |
Fri, 11 Sep 2015 19:29:24 -0700 (PDT) | |
Date: | Fri, 11 Sep 2015 18:29:24 -0800 |
Message-ID: | <CAC4O8c_XFEAgyrokrwwavB0C+OjWXCB5xptkVwMx2i_t960qFg@mail.gmail.com> |
Subject: | [geda-user] shortest way towards parsing .pcb files outside pcb |
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 |
Roland Lutz <rlutz AT hedmen DOT org> wrote: > This is just what I did with Xorn for schematic files: > > xorn.storage - in-memory representation of schematic objects > xorn.geda.read - reads .sch/.sym files > xorn.geda.write - writes .sch/.sym files > xorn.geda.netlist - creates netlists from schematic files > xorn.geda.render - renders schematics to Cairo for display and PDF export (work in progress) > > The obvious thing would be to continue that scheme for PCB, too: > > xorn.storage - in-memory representation of PCB objects > xorn.pcb.read - reads .pcb files > xorn.pcb.write - writes .pcb files Is this something that's about to happen? If so I'll stop working on wrapping the parser from PCB. Speaking of the parser, I think the easiest way to get an accessible version of it would be to add a structure that corresponds one-to-one with what goes in a .pcb file. The parser could load stuff into that. The current "PCBType" structure (really a sort of global application context) could be filled in from that structure, rather than incrementally during the parse. Would this offend anyone?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |