 | | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) I believe Lar mad the case that the SB can/should include people from all camps. I for the most part agree, because we need perspectives from the various types of people who create [elements of] and use this system. -Tim (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Charter Org for LDraw.org (was: Re: LDraw Versioning (Was Re: Backwards Compatibility))
|
|
(...) Cool. I put 'nonprofit' in to emphasize the nature of the organization. While I've taken a cursory look at information on "nonprofit corporations," I'm not totally aware of alternatives. Obviously, we want to travel down the route that creates (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) ... and no. IMO, if the meta statement isn't listed in the current file format document, it's open to change. The meta-commands on that document (pulling from memory): STEP, PRINT, WRITE, SAVE (?!), (I gave up, dug out the code) PAUSE, CLEAR, (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) can snag a copy of that. Steve (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Right. But newer OS's and video cards are becoming less compatible with DOS programs, especially DOS programs that do graphics. I used to be able to run LDraw with Super-VGA resolutions (with Win95, I think). I haven't been able to that in (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | 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)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) I really agree with Dan on this point. As I mentioned in another message, a standards body could certainly come up with suggestions for standard commands, but they wouldn't have any power of enforcement. About the only thing ldraw.org could[1] (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) Because it wouldn't be supported by LDraw and LEdit. Part files frequently include comments, so any standard option for commenting should be allowable in the parts library. (...) Some people already use COMMENT. Steve (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) Rosco, Unfortunately, MLCAD's use of WRITE is a really bad example, because MLCAD is mis-using an already standard meta-command. Plus, 0 WRITE statements are not allowed in official parts, so any part authors who create their files in MLCAD (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) I support that (general) guideline. The only real difficulty is if the meta-command becomes generally accepted, and is 'promoted' to being an accepted standard. We'd either want a different prefix for org standards, or no prefix. Either way (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) I agree with Larry -- support it publically. Recognize '0 LTrax xxxx' as the primary syntax for the command. Especially, let the author of the original command know that you are implement their command. Hopefully, that will give them cause to (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
