Very interesting, this setup is very similar to some of the info I use with LDCad part snapping.
The biggest difference being I'm using (cylindrical) shape description as much as possible but for the more weird things (glass, nxt connector, etc) I too fall back on group based male/female matching.
And instead of XML i use LDraw meta's in a second library tree so you can edit/add info on a loose per .dat basis.
I'm curious I choose the shape description method in order to deal with parts like 32209.dat (axle with non axle section in the middle), it's definition in LDCad is like so:
How would JBrickBuilder define such a part?
The biggest difference being I'm using (cylindrical) shape description as much as possible but for the more weird things (glass, nxt connector, etc) I too fall back on group based male/female matching.
And instead of XML i use LDraw meta's in a second library tree so you can edit/add info on a loose per .dat basis.
I'm curious I choose the shape description method in order to deal with parts like 32209.dat (axle with non axle section in the middle), it's definition in LDCad is like so:
Code:
0 !LDCAD SNAP_CLEAR
0 !LDCAD SNAP_CYL [gender=M] [caps=none] [secs=A 6 18 R 8 2 R 6 8 A 6 80] [center=true] [pos=-1 0 0] [ori=0 -1 0 1 0 0 0 0 1] [slide=true]How would JBrickBuilder define such a part?