[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: gEDA-user: Solving the light/heavy symbol problem

I'd like to note that we have a serious power tool in gnetlist, and it's not too hard to get it to translate attributes. Here's an example:

Attachment: gnetplug-metadata.scm
Description: Binary data

Attachment: project_metadata.scm
Description: Binary data

Attachment: metademo.sch
Description: Binary data


gnetlist -l project_metadata.scm -g your_favorite_back_end metademo.sch

"project_metadata" is a project-specific file, while gnetplug-metadata.scm defines the simple machinery that makes this work.

A next step might be to have a parser for a rule format that's more tabular and spreadsheet-friendly than S-expressions, although "cargo cult" construction of rules from the example here shouldn't be too hard.

This could be a fine mechanism for manipulating invisible attributes like footprints. It can't do annotation because gnetlist hides much of the schematic data from the back-end script. There is an annotation tool that's conceptually like gnetlist at https://github.com/xcthulhu/lambda-geda. It converts schematic format to/from S-expressions for processing with a "back end", but it's written in Haskell, which I guess would be even more of a barrier than Scheme. It is, however, in production use at Noqsi and Osaka, creating flattened schematics for documentation. Consider it "proof of concept" for an annotation tool.

John Doty              Noqsi Aerospace, Ltd.

geda-user mailing list