 | | Re: Latest BFC Spec?
|
|
(...) Hmm. To tell you the truth, I don't remember. My main use for it is to make sure patterns are rendered on the backside of transparent solids. I will *allow* that NOCLIP/CLIP can be used to allow non-compliant sections of code, but I don't feel (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Latest BFC Spec?
|
|
(...) Absolutely. :) The spec was never ratified or 'officially' accepted as a standard. Parts of it are have definitely evolved as the defacto standard, but that's not the same as having a good, documented standard to follow. I think the spec can (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Latest BFC Spec?
|
|
(...) I could kind of see that, but not in the parts library. I would expect that any file in the library that specifies NOCLIP does it for a good reason, and should not be overrode (overridden?). What I could maybe see in the parts library is a (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Latest BFC Spec?
|
|
(...) During the rendering process, it is necessary to keep track of both the 'accumulated clip-state' and the 'local clip-state'. The accumulated clip-state is logically equivalent to boolean ANDing the local clip-states of all the parent files. As (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Charter Org for LDraw.org (was: Re: LDraw Versioning (Was Re: Backwards Compatibility))
|
|
In lugnet.cad.dev, Tim Courtney wrote: [snippity-do-dah] (...) Whoa there! There is a *huge* difference between a 'formal organization' and a 'formal nonprofit organization'. If you were using 'nonprofit' informally, please *don't*. 'nonprofit' (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) I agree. (...) Nit: we've already *got* an LDraw file format spec. Next item! (...) 'Control' is heavy-handed for my tastes. 'Support', 'endorse', 'coordinate' are all better. All a standards body could do is manage the documentation, and (...) (22 years ago, 21-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Dan, You program in *Perl*. Of course you think it's good to always have punctuation. You probably think more punctuation == better. ;) Steve (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) True, but that's no reason to have (unnecessary) complications. The computer will understand whatever we set it up to understand. LIGHTVALS, {LIGHTVALS}, 32.6, it's all the same to the silicon. Syntax is for users, beginning or advanced. If we (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Depends on how open or closed the SB is. I think there's a place for part authors and users as well as developers. Steve (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Tim, I've been reading this thread, and you keep mentioning this 'Steve' person. 'Steve this' and 'Steve that'. I must have gone through 100 messages by now, and no 'Steve' has shown up. I'm beginning to suspect you are imagining this 'Steve' (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
