Subject:
|
Re: Color page updated
|
Newsgroups:
|
lugnet.cad.dev.org.ldraw
|
Date:
|
Thu, 3 Dec 2009 18:48:35 GMT
|
Viewed:
|
17528 times
|
| |
|
|
In lugnet.cad.dev.org.ldraw, Andrew Westrate wrote:
> In lugnet.cad.dev.org.ldraw, Scott Wardlaw wrote:
> > I think we are loosing sight of the purpose of LDconfig.ldr...
> >
> > The LDconfig file is meant to be a quick cheat sheet... it is meant to help
> > standardize the colors used through easy to use Color Codes. It is meant to be
> > made up of colors that everyone can recognize. These colors are simply, the
> > colors of LEGO parts that exist in the real world.
>
> I disagree that this was the original purpose of the ldconfig file. I can say
> that definitively, since I was the one who first proposed the file here:
> <http://news.lugnet.com/cad/?n=10066>. The purpose was that when *new* colors
> were added, ldraw software tools would have a standardized way of supporting the
> new colors. It wasn't meant to limit the available ldraw colors to the actual
> shades of plastic used, or to make the dithered color ranges no longer valid.
I never said that it was meant to limit, only that it is made up of these colors
now. Please don't take this to mean that new colors can't be added, or that it
invalidates other colors. We already know of at least one color that should be
added for the next release. If you know of more that should be added, please
let us know (but don't say every color under the rainbow)
> > However, if you want a part to have a color that is not in LDconfig, you can
> > still spell out the RGB values instead of using the Color Codes. LDconfig is a
> > reference for standard colors and does not limit you to only using these colors.
>
> I have never seen an official LDraw part that defines a custom RGB color, nor
> any part on the part tracker do that. How would you even do it? I don't know
> the syntax, and haven't found any part tracker documentation saying what the
> syntax is or saying it's ok for official parts.
>
> Plus, how many programs actually support custom-defined colors? If this becomes
> the mandatory way for part authors to do printed parts, how many programs are
> going to be broken?
That is correct, and you probably won't ever find an official part with RGB
values instead of a Color Code. I have made several sticker parts with RGB
values instead of Color Codes, but these are for my personal use, not official.
Again, if you have a specific RGB that you believe should be added to LDconfig,
please let us know.
> > C) The transparent colors that are missing don't actually exist in the real
> > world. The ones that you are refering to were made from the original 16 colors
> > - not actually from real LEGO colors. The transparent colors that are included
> > in LDconfig actually exist in real life. If you do happen to find a real brick
> > with a color that is not in LDconfig; please let us know.
> >
> > Likewise with the dithered colors. This system was a quick (and worthy)
> > solution when it was created. In recent years, it has caused a great deal of
> > problems. Again, these colors don't exist in real bricks, so should not be
> > included as colors that LDraw recognizes as a standard.
>
> Once again, it is a mistaken assumption that the LDraw color codes apply only to
> actual brick colors. The the LDraw color codes have to allow for any color of
> line or polygon which appears in a part file, be it plastic, rubber, metal,
> printing, or sticker color. By saying that any part using a color in the
> dithered color range is no longer allowed on the part tracker, we are seriously
> limiting the ability of part authors to render a "good enough" approximation of
> stickers and printed parts.
Sorry, instead of real bricks, I meant real LEGO pieces. This can mean printed
bricks, stickers, rubber, etc. You'll note that these have already been added
when they were needed, such as Electric_Contact_Alloy, Rubber_White, etc.
|
|
Message has 1 Reply:
 | | 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)
|
Message is in Reply To:
| | Re: Color page updated
|
| (...) I disagree that this was the original purpose of the ldconfig file. I can say that definitively, since I was the one who first proposed the file here: (URL). The purpose was that when *new* colors were added, ldraw software tools would have a (...) (15 years ago, 3-Dec-09, to lugnet.cad.dev.org.ldraw)
|
28 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
