Does anyone have contact info for the remaining people listed on this page?

https://code.google.com/p/datsville/wiki...enseStatus

Please PM me if you do. Thanks.

A little detail that just caught my eye: The banner image and text on Parts tracker is different from other parts of the site.
Most pages have the same image of a partly transparent 2x3 brick and the text "LDraw.org Centralised LDraw Resources" in British English spelling. The image on Parts Tracker is similar but without the inner tube and with a slightly different colour and camera angle, and it has the text in American spelling: "Centralized LDraw Resources".

If I want to do a prism primitive similar to tri3a1, but with one right-angle side and the diagonal side, what should that be called?
In general, what is the naming scheme for primitives? Looking at all the various cube-based primitives I haven't found the logic yet...

I've turned the conversion of bare URLs to hyperlinks back on. Please be aware of the URL in enclosed in double quotes bug mentioned here: http://forums.ldraw.org/showthread.php?tid=2483

I would like to request Part number 6089 (The Aquashark helmet), since this part is too complicated for me to make.
http://www.bricklink.com/catalogItem.asp?P=6089

I would also like to make a request on these two parts:
http://www.bricklink.com/catalogItem.asp?P=x199
http://www.bricklink.com/catalogItem.asp?P=6919

I am currently doing a lot of the patterned parts from the aquazone theme and some of the older space sets, and it could be great if someone could make the few remaining, non-patterned, parts from these lines.

I noticed that Tore Eriksson "inlined" a lot of parts in Datsville in the past. I'm not sure exactly what that means, but I'm guessing it means removing a model from a sub-assembly and placing it in a higher-level parent model without messing up the model's position.

I would like to do the same. I would like to extract minifigures from within individual MPD models and place them in a higher "traffic" layer without screwing up their positions.

Am I being clear? How do I accomplish this?

Whenever I load Datsville I get this error for a missing part:



How do I fix this?

In this video the person uses I think three different shades of green. I could only find one shade in MLCad plus chrome green and trans green. Is there a list of colors somewhere I need to update? Where do I get the latest version?

It makes no difference if I select "Open" or "Download" for an attachment. Either case causes the download dialog to appear.

Using Chrome 31.0.1650.48 m on Windows 7 64 bit.

At part
http://www.ldraw.org/cgi-bin/ptdetail.cg...343c02.dat
on the parts tracker, an important question got raised,
which is probably complicated to discuss, so I suggest to relocate it to here:

the problem is: what filename should we assign to assemblies?

let's assume we have a door 4343.dat, and a glass 4344.dat.

Let me describe the common practice of the past first:

Our technique was - not knowing official TLG item or design IDs -
to use the "main" part, here: the door, of the assembly and number the assembly after it.
Thus, in our case, 4343c01.dat was the result.
In some assemblies it's unclear what the "main", "dominant" contributing part is, but you have to make a decision.
In that assembly, that main part usually gets color 16 to still let the user colorize it as desired.

NOWADAYS we do know some of the item or design IDs of such assemblies.

The question that now arises is how we deal with that. Let's assume, we somehow know that the assembly
should get number 123456789. What to do now?
The options we have is:
(a) abolish the ...c01 suffix technique at all in this case, just using 123456789.dat for the assembly
(b) keeping the old technique, i.e., 4343c01.dat, and creating an alias 123456789.dat pointing to there
© using 123456789c01.dat, i.e., mixing the 2 concepts

Sadly, all 3 options have disadvantages
Solution (a) drops 2 nice features of our library:
- you can recognize from the filename to which part an assembly belongs to, i.e. 4343c01.dat belongs to 4343.dat
- the ...c01 suffix is nicely matching the ...s01 and ...p01 and ...d01 suffixes
Solution (b) creates 2 files instead of 1.
Solution © is IMHO totally misleading. It suggests that 123456789c01.dat contains an assembly of 123456789.dat, i.e., an assembly of an assembly. So to me, this is the weakest of all 3 options.

To me, the smallest disadvantage is solution (b), because we anyway create shortcuts and aliases all the time.
Would we correctly create 123456789.dat as an alias, having a leading "=" in its name, then users even can
leave away such files if they find them to be clutter.

So my opinion is to use option (b).