Hey Mattia,
it is good to see, that someone is engaging with this topic again. I really like what you are planning and I will try to contribute.
But first of all, I would like to ask you to clean up the file a bit. There are double entries for both, bricks and transformations (excuse the monoton format, it is an output from an applicaiton):
Then there are a lot of brick entries that are useless:
For many of the transformations the LDraw part does not even exist. E.g.:
From my point of view these placeholders (or at least I think that they are placeholders) will only confuse on the completeness
of the ldraw.xml and could guide to LDraw files, that contain wrong lines or lines for parts, that do not exist (I did not check
how the LDD handles them).
Btw, does the LDD use the <Assembly>-tags?
Rolf
it is good to see, that someone is engaging with this topic again. I really like what you are planning and I will try to contribute.
But first of all, I would like to ask you to clean up the file a bit. There are double entries for both, bricks and transformations (excuse the monoton format, it is an output from an applicaiton):
Code:
Multible definitions for the Brick 61252.
Multible definitions for the Brick xxx.
Multible definitions for the Transformation 6019.dat.
Multible definitions for the Transformation 41855.dat.
Multible definitions for the Transformation 2516.dat.
Multible definitions for the Transformation 2413.dat.
Multible definitions for the Transformation 57518.dat.
Multible definitions for the Transformation 92339.dat.
Multible definitions for the Transformation 45106.dat.
Multible definitions for the Transformation 54090.dat.
Multible definitions for the Transformation 3626bpa8.dat.
Multible definitions for the Transformation 54654.dat.
Multible definitions for the Transformation 54923.dat.
Multible definitions for the Transformation 64248.dat.
Multible definitions for the Transformation 30225b.dat.
Multible definitions for the Transformation 92088.dat.
Multible definitions for the Transformation 64783.dat.
Multible definitions for the Transformation 3641.dat.
Multible definitions for the Transformation 4003.dat.
Multible definitions for the Transformation 95320.dat.
Multible definitions for the Transformation 2531.dat.
Multible definitions for the Transformation 98376.dat.
Multible definitions for the Transformation 54090.dat.
Multible definitions for the Transformation 60779.dat.
Multible definitions for the Transformation 88287.dat.
Multible definitions for the Transformation 85944.dat.
Multible definitions for the Transformation 64797.dat.
Multible definitions for the Transformation 98366.dat.
Multible definitions for the Transformation 4505.dat.
Multible definitions for the Transformation 10173.dat.
Multible definitions for the Transformation 41881.dat.
Multible definitions for the Transformation 85948.dat.
Multible definitions for the Transformation XXXX.dat.
Multible definitions for the Transformation 2339.dat.
Multible definitions for the Transformation 76254.dat.
Multible definitions for the Transformation 30413.dat.Then there are a lot of brick entries that are useless:
Code:
<Brick ldraw="XXXXX.dat" lego="xxxx" />
<Brick ldraw="XXXXX.dat" lego="XXXXX" />For many of the transformations the LDraw part does not even exist. E.g.:
Code:
<Transformation ldraw="13250.dat" tx="0" ty="0" tz="0" ax="0" ay="1" az="0" angle="3.141593"/>From my point of view these placeholders (or at least I think that they are placeholders) will only confuse on the completeness
of the ldraw.xml and could guide to LDraw files, that contain wrong lines or lines for parts, that do not exist (I did not check
how the LDD handles them).
Btw, does the LDD use the <Assembly>-tags?
Rolf