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

Re: gEDA-user: next PCB release - 1.99za vs 4.0

DJ Delorie wrote:

Now, the question becomes "which is more fundamental?".  I think
it's geometry.


A hole is the same geometry regardless of what level of the heirarchy
it's placed at.  So let me rephrase: Why have seven geometric holes,
one for each layer, when we can have one geometric hole applied to the
whole composite
{ "layer_order" : ["top", 2, 3, 4, "GND", 6, 7, 8, "PWR", 10, 11, 12, "bottom"] } 
...
{ "via" : [3, "PWR"], "pos": [86400, 1440], "size" : [2000, 3500, 4500, 4000, 5000] }
That's about how it would look for me in JSON. The via can be nested in a group 
block or whatever, or just relative to the board as now.
For those that like it more bloated it can of course be defined as:
{
   "object_type" : "via"
   "layer_range" : [3, "PWR"],
   "location_of_center" : [86400, 1440],
   "bore_diameter" : 2000,
   "outer_copper_diameter" : 3500,
   "outer_copper_clearance" : 4500,
   "inner_copper_diameter" : 4000,
   "inner_copper_clearance" : 5000
}
which is still JSON.
And now, how the generic, object oriented, naming-convention-abiding, Perl-tweaking XML guys like it: 
<geometrical_object><object_type>via<\object_type><object_properties><prop_via_layer_range_start>3<\prop_via_layer_range_start><prop_via_layer_range_end>"PWR"<\prop_via_layer_range_end><prop_via_location_of_center_X>86400<\prop_via_location_of_center_X><prop_via_location_of_center_Y>1440<\prop_via_location_of_center_Y><prop_via_bore_diameter>...

Have fun with verifying, that the Perl tweak got it right ;-)
(Btw. I love Perl and use is quite often)


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