| |
In lugnet.cad, Jake McKee wrote:
| |
I could be totally off base, but my thinking is that some group has to “own”
the naming/numbering, and what better group than LDraw.org? (With input from
relevant players, of course)
|
I do not think anybody would need to “own” anything here (other than Lego). And
I do not think any one site should be the leader with this. If the 3 sites chose
to work something out then they should all have an equal say. As catalog admin
on BL I would not want to be flat out told what to name something with less
input than the next person, and that really turns me off to the idea (speaking
for myself, not anybody else in any way mind you). I think that was the problem
last time - one site trying to take everything over.
I also think that before the community can ‘come together’ on this Lego needs to
‘come together’ with itself first. I am not sure how something can be expected
when a company uses the same name for 2 different colors in one example, and 2
names for the same color in another example.
I am not saying Lego needs to change its internal names - but it would be good
to see a color guide ON lego.com that uses public-friendly names (and dare I say
more correct names than the internal names?). And this would include STOP using
a name for a color when that color has been changed - example - NOT calling the
new bley ‘gray’. As well as only using ONE name per color (example of green and
dark green).
Do not get me wrong - I think its a great idea - but I would like to see Lego
get useable names first.
Mark P
LoB
|
|
Message has 3 Replies:
 | | Re: Color Names
|
| (...) All I mean by "own" (and the reason I keep using quotes) is that someone/some group is driving the process. And as I, and I believe Steve and Tim mentioned, the point I was making wasn't that anyone is told what to do, but that there is input (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego, FTX)
| | | Re: Color Names
|
| "Mark P" <mark@landofbricks.com> wrote in message news:Hz45ux.3JA@lugnet.com... (...) "own" (...) from (...) Lego). And (...) chose (...) admin (...) less (...) (speaking (...) problem (...) needs to (...) expected (...) and 2 (...) good (...) I (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego)
| | | Re: Color Names
|
| (...) I don't think I follow your point. LDraw/Peeron are (almost) synchronized in terms of parts. They're somewhat synchronized on colors and try to be. Bricklink uses (from my point of view) incompatible part names and incompatible color names. If (...) (20 years ago, 11-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego)
|
Message is in Reply To:
| | Re: Color Names
|
| (...) I know it's not, by definition, a LSC issue, but perhaps it should be. Much of the cross-site element "system" has been based on LDraw's part numbering and whatnot. If you look at Peeron, for instance, the parts are listed by their LDraw (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego, FTX)
|
20 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
|
|
|
|
