 | | Re: Opinions needed for Color and Edge Values
|
|
(...) We should be able to have TLG names as a language file, since every TLG color value should map to every BL (BrickLink) color value. I certainly understand the drive to have them in the file in one form or another. Perhaps the most benefit can (...) (17 years ago, 25-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) I am _strongly_ against that. Imho this is the same mistake LEGO did a few years ago with the stone colors. What would be the point of defining a standard (ldconfig.ldr) to change it at the first drawback? Colors 70..72 are defined for more (...) (17 years ago, 25-Nov-08, to lugnet.cad)
|
| |
| | Re: LDraw (and LDraw.org) questions
|
|
(...) This has never been implemented. The SteerCo has had some discussions about also considering to use the wiki for the OMR but never reached consensus. IMHO I'd rather have a module for the CMS taking for granted that I'm not talking about a (...) (17 years ago, 25-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) I'd like to hear some opinions on how we do define backwards compatibility? Considering that most user built their models using MLCad (no idea which color numbers are supported by Leo, Bricksmith or SR3D) which comes with very limited color (...) (17 years ago, 25-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) The "besides the color code" isn’t a collateral damage but the main problem! We cannot ship the TLG numbering in a simple language file. Think about a blue car colored with LDraw code 1. Loading the TLG colors as language file you would (...) (17 years ago, 25-Nov-08, to lugnet.cad)
|
