Re: gEDA-dev: footprint cleanup

[DJ Delorie <dj@xxxxxxxxxxx>]

> This why i suggest something hid-like for elements. One module would use
> newlib (just reading the file and return its content trough the api),
> another would run m4 or whatever and return the content generated trough
> the same api.

I like the way perl does it.  If you specify a file name, it gets
loaded.  If you prefix a string with "|", it popen's the remainder and
reads the output.  We do something like this internally (we don't call
m4, we call QueryLibrary.sh) but it would be nice to move the "footprint
name" further up the chain and get rid of the knowledge of QueryLibrary.sh.

Thus, we could have a footprint of "|./make-tssop -q 0.40 -n 64"

Similarly for load and save.  We currently *always* use some popen,
even if it's just "cat".


_______________________________________________
geda-dev mailing list
geda-dev@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev