 | | Re: LDraw.org Bylaws - new proposed clauses
|
|
(...) After giving some thought to this - I can't think of alternate wording that would really do the issue justice, and not end up unnecessarily lengthy and awkward. If we start looking for CoI under every rock, I think that's taking it too far. My (...) (21 years ago, 6-Feb-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I don't want to specify that some parameters are order-specific, and others aren't. I'd rather they are all one way or the other. Goes back to easier 'correct' parsing. However, I'm sure the entries in ldconfig.ldr will always have their tags (...) (21 years ago, 6-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) Actually, the spec says just the opposite, that tags (keywords) are not case-sensitive: (...) That seems reasonable. Steve (21 years ago, 6-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) Actually, I've most recently used dithering to simulate chrome/metal/metallic parts. Steve (21 years ago, 6-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) OK, I'm alright with that. (...) If that's a needed parameter, I'd rather have it follow the METALLIC keyword. (...) I'm ok with that, too. Is '50%' really an adequate description? There can be many brush patterns... Steve (21 years ago, 6-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) There had been discussion previously about differentiating true comments from meta-statements. The LSC agreed that it seems like a good idea to start prefixing meta-keywords with a punctuation mark, and we chose !. And !COLOUR is shorter than (...) (21 years ago, 6-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) Actually, I was considering the possibility of (patterned) parts including custom color definitions, which would only apply to that part. (...) That's a good question. Think about this: what if file A also has some surfaces hard-coded to color (...) (21 years ago, 6-Feb-04, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Bylaws - new proposed clauses
|
|
(...) I don't think we could list which companies to watch out for, and which not to, and be comprehensive. That's why there's a general removal clause in 6.04 to enable the members to remove a SteerCo member in cases of documented, serious (...) (21 years ago, 5-Feb-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: LDraw.org Bylaws - new proposed clauses
|
|
(...) What about MegaBloks, or any other company that may have an interest? Why pointing the finger on TLC only? Why not have a more general clause about conflict of interest? -- Anders Isaksson, Sweden BlockCAD: (2 URLs) (21 years ago, 4-Feb-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: LDraw.org Bylaws Drafts: Call for Public Discussion and Consensus
|
|
(...) Thanks for your confidence. Based on my experience in the company so far, working relationships I have with Community Development people, and experience in the hobby in general, I do not believe the pressure you hypothesize about is likely to (...) (21 years ago, 4-Feb-04, to lugnet.cad.dev.org.ldraw, FTX)
|
