 | | Re: Help writing LDraw's history
|
|
(...) Really great work! I would have liked to contribute to the article by writing in it, but I'm aware that my English is far from perfect. So I just add some of my thoughts as an input. The main focus seems to be on the various administrational, (...) (15 years ago, 11-Dec-09, to lugnet.cad, lugnet.cad.dev.org.ldraw)
|
| |
| | Help writing LDraw's history
|
|
Guys, quoting Jim Morrison (The Doors) I'd say: "The end is near". Obviously I'm talking just about 2009. Updating LDraw's history page: (URL) have to admit that I've forgotten to update the page last year. I would appreciate if you could fill in (...) (15 years ago, 11-Dec-09, to lugnet.cad, lugnet.cad.dev.org.ldraw)
|
| |
| | LDraw.org's November 2009 Part of the Month Winners
|
|
Congratulations to the winners of the November 2009 Part Of The Month (POTM) contests: (URL) POTM - Best Part, Electric Power Functions IR Handset Incremental (Complete) by Philippe Hurbain (Philo)> (URL) POTM - Most Desired Part, Tyre 37 x 22 ZR by (...) (15 years ago, 8-Dec-09, to lugnet.cad, lugnet.cad.dev.org.ldraw, lugnet.announce, FTX)
|
| |
| | Re: Color page updated
|
|
(...) OK, I'll update my programs to use this algoritm for colors not stated in ldconfig.ldr /Lars (15 years ago, 7-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) SKIPPING "C:\LDraw\ldconfig.ldr" Line 40: Illegal color code: 0 !COLOUR Main_Color CODE 16 VALUE #7F7F7F EDGE #333333 SKIPPING "C:\LDraw\ldconfig.ldr" Line 54: Illegal color code: 0 !COLOUR Edge_Color CODE 24 VALUE #7F7F7F EDGE #333333 WARNING (...) (15 years ago, 7-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) I'm gonna explain (and quit afterwards) why I hesitate adding new and old - what I call "MLCad" - colors to the LDConfig.ldr file: * The current LDConfig.ldr contains only colors you'll find in official LEGO Bricks (with two exceptions (...) (15 years ago, 6-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) Hi Steve, good to hear from you again. Would you mind lokking into this: (URL) (15 years ago, 5-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) Tore, Feel free to add any color, RGB, name or number you like to the LDConfig.ldr. file. I really won't stand in the way of 100% backwards compatibility to L3Lab. w. (15 years ago, 5-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) Oh. Oh. I... I wish somebody had told me this before, instead of arrogant and provoking things like: "Welcome to 2009". Or maybe someone has tried, but I've been the write protected that time? /Tore (15 years ago, 5-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) Yes, exactly. 48 is rendered as trans-black, 65 is blue, and 133 should be dark pink (or whatever we're calling color #5 today). Steve (15 years ago, 5-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) Do you mean that original LDraw accepts color 48, 65, 133 without error message? I didn't know that. Pity L3Lab (and L3P v1.3 which I no longer use)don't act that way. If so, I guess I stand corrected. And blushing. But yet, with a little (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) Just to be clear: all colors from 0 to 511 (except 16 and 24) are true LDraw colors. For color codes less than 256, LDraw would use the lowest 4 bits to determine the color value. The sixth bit would determine transparency. The other bits were (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) I for one would have been very happy with that approach. That's exactly what I have tried to tell over and over and over again. Could those of you who have their intellectual write protection on, pretty pretty please unlock it for just a few (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
Nobody ever listens to me on the issue of colors, but that doesn't mean I'll go quietly... (...) I don't see why they need to be added to the ldConfig file as long as they're documented somewhere and accepted as the standard default LDraw pallette. (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) Sorry, but I really cannot understand the need to encode dithered colors. Personally I think that only colors used for parts should be coded, while, when you create a patterned part you can choose to use a "good enough" already coded color or (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) It might fix it (I think it would still gum up the PT with over-zealous hold votes); but why break anything when we're just talking about adding fewer than 200 lines to the config file? I think it's a terrible idea to make dozens of (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw, FTX)
|
| |
| | Re: Color page updated
|
|
(...) I have had parts on the Part Tracker held because they used one of these colors. That means it is limiting. (...) Color numbers 32-47 and 256-511 is not every color under the rainbow. (...) This is exactly the problem. (...) If this is the (...) (15 years ago, 4-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) There are already two very old ways to specify RGB colors in LDraw files. One comes from ldlite with somewhere between 12 and 15 effective bits of color information, and the other from L3Lab/L3P with 24 bits of color information. If we're (...) (15 years ago, 3-Dec-09, to lugnet.cad.dev.org.ldraw, FTX)
|
| |
| | Re: Color page updated
|
|
(...) Of course it would - as well as it does LDView. But after adding x, y, z coordinates and correcting RGB code syntax would work fine with both LDView as well as L3Lab! 1 0x02F2F2F2 0 0 0 1 0 0 0 1 0 0 0 1 part.dat Don't know about MLCad, but I (...) (15 years ago, 3-Dec-09, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Color page updated
|
|
(...) Neither did I but if you really cannot find a suitable color for your pattern an RGB say in the form: 1 #F2F2F2 1 0 0 0 1 0 0 0 1 part.dat would surely solve your problem. And I'm going to propose this to the new elected LSC. As for the broken (...) (15 years ago, 3-Dec-09, to lugnet.cad.dev.org.ldraw, FTX)
|
