 | | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
Quoting Tim Courtney <tim@zacktron.com>: (...) I disagree. How can you prevent the various programmers from adding new functionality to their software? Why should development on all these tools halt until the non-existent committee figure out what's (...) (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) No, I'm saying that if anyone is thinking about adding a meta-command they need to, at the very least, post what they plan to add so that the community can comment and ultimatly say yea or nay. Once the committee us up a running thay will take (...) (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) the more I think about it, the less sense it makes to me. The community (or the "board") could suggest names, and keep track of what's out there - but a "yea or nay" power seems excessive. How, exactly, do you propose you enforce this "nay"? I (...) (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) I agree 100%. -Tim (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Point taken, but I still think developers should discuss what they want to add with LDraw.org and Lugnet.cad.dev so that they don't add something that's already been added or being developed. -Orion (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) I agree that the discussion should take place - I'm just worried about the "regulation" part. Dan (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) No, I think the intention is to create an official set of meta-commands, which official software should recognise and/or implement. The important point being that any file containing non-ratified commands will not make it into the official (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Well this was one of the reasons behind my original suggestion. (This thread sure did take off while I was away skiing this weekend.) I suggested that a new meta command group be made today, albeit before the creation of a standards body, so (...) (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) I disagree. Let's stick with the current method of meta-commands until a standards body officially determines the syntax of future generation commands. No hold on anything, innovation can continue (just in the same disorganized fashion it (...) (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) That's fine also. I was only offering a possible way to avoid taking even more useful options away from the standards commitee. I don't think it would be too much to ask that new commands all be prefixed with 'UNOFF' or 'UNOFFICIAL'. It of (...) (22 years ago, 17-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Understood. I think we need to focus on creating legitimacy for making decisions on standards before actually making decisions on standards. ;-) (...) That's a resonable request. Here's some thoughts -- I think the standards body will be (...) (22 years ago, 17-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: 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)
|
|
(...) 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: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Very good point. In my conversations with a few semi-outsiders to the LDraw community, they believed systems could (or should, I see your [1] and rase you that) be established to encourage participation and compliance, but could not/should not (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
But, isn't that more-or-less exactly what happens with the parts library? (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Not really. The important thing with the parts library is that files are accepted and added the distribution file. We don't even have a '0 Official' any more - now it's '0 LDRAW_ORG'. I was envisioning the 'LDraw.org Compatible' program to be (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
In lugnet.cad.dev, Steve Bliss writes: <snip> (...) <snip> (...) The point of setting an 'LDraw.org Compatible' format would be to set the framework of LDraw files, not to restrict what can be in LDraw files. If a programmer wants to implement thier (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) LDraw compatible, or LDraw.org compatible? ;-) You made a distinction before -- are you using the same metric now as well? Just curious. -Tim (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Sorry, 'LDraw.org-compatible programs'. Which is poor terminology, I think. Steve (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) I agree. I don't think a program can be "compatible" with an organization. It can be "certified" by one, though: LDraw.org-Certified. Of course, this might have stronger implications than LDraw.org-compatible. On the other hand, maybe that's a (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Exactly. -Tim (22 years ago, 23-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Certified does sound better in that context, and I think certification could be a good thing. We should figure out how best to frame it, but I think it would add to the strength and usefulness of LDraw.org as a central resource for all of (...) (22 years ago, 23-Mar-03, to lugnet.cad.dev)
|
