 | | Re: Unified installer
|
|
(...) Ah, I clicked on the "Download" link (bolded) on the ldraw.org sidebar and didn't see it anywhere. It is listed in the "Getting Started" section instead. -Mike (16 years ago, 29-Nov-08, to lugnet.cad)
|
| |
| | Re: Unified installer
|
|
(...) The LDRAW ALL-IN-ONE-INSATLLER does this already. The user gets to choose 1 of 3 options. 1) BASIC install which installed LDRAW Part libary, MLCAD, and LDVIEW 2) INTERMEDIATE which installs BASIC + L3P, L3PA, LPUB, LGEO and POV-Ray 3.1g and (...) (16 years ago, 28-Nov-08, to lugnet.cad)
|
| |
| | Re: Unified installer
|
|
(...) This problem has been indintified a long ago, but a quick solution was blocked by the fact that several of the included part files are historicly not licenced for distribution in another form then included within the original LDraw Package. In (...) (16 years ago, 26-Nov-08, to lugnet.cad, FTX)
|
| |
| | Unified installer
|
|
I think the way that the LDraw utilities are installed is a bit complicated for novice users, especially children or parents of children. Essentially, the current scheme asks users to first install the resources required by the software, and *then* (...) (16 years ago, 25-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) I completely agree that changing the colour codes at this stage is a terrible idea. However I have nothing against duplicating them. One thing we do need is to maintain, alongside the LDraw codes, mapping lists to other known systems such as (...) (16 years ago, 25-Nov-08, to lugnet.cad)
|
| |
| | Re: Opinions needed for Color and Edge Values
|
|
(...) Since MLCAD (and other programs) do not support color codes above 511, a different approach to reading TLG colors is needed. However, I have to strongly agree with Philo. Changing color codes that have been defined for years is not a good (...) (16 years ago, 25-Nov-08, to lugnet.cad)
|
| |
| | 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 (...) (16 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 (...) (16 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 (...) (16 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 (...) (16 years ago, 25-Nov-08, to lugnet.cad)
|
