| | 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)
|