Philip Pemberton wrote: > It is a LOT more verbose than what I proposed. I'd rather have a > single-line description to create a component,
Me too :-) Just think of doing some simple processing with a shell script or tools like grep. With XML, you're forced to use/write considerably more complex tools. > I guess you could always > write a Perl, Bash or Python script to write the component script... :) By the way, I tried the approach of programmatically generating components: http://svn.openmoko.org/developers/werner/gta02-core/components/kifps.pl I experienced mainly two problems: - it's often hard to imagine the whole geometry, so one has to make a sketch. That sketch is basically the documentation that explains how the script works, but would you make the effort of making it clean enough that others can read it, and make sure it doesn't get separated from the program ? - you won't now what exactly your script did before you load it into the component editor and measure everything That's why I wrote fped, which has a visual representation of everything it does (you're free to forego the GUI and just "program" the definition, and it'll still do the sketch for you) while still supporting constructs typically found in programming languages, and - perhaps even more important - it lets you specify automatic measurements. - Werner
