 | | Re: Calling all Meta-commands —Larry Pieniazek
|
| | | (...) One thing that I think would help reduce namespace pollution is if everyone did what LTrax did... prefix the command with the app name for uniqueness. Not a perfect solution, of course. (22 years ago, 14-Mar-03, to lugnet.cad.dev)
|
| | | |
| | | | | Re: Calling all Meta-commands —Dan Boger
|
| | | | | (...) except that if you do that, it discourages cross-tool commands. If I'm writing FooCAD, and I want to implement one of the LTrax commands, should I make a new command '0 FooCad xxxx'? should I secretly support the '0 LTrax xxxx'? I'm not sure (...) (22 years ago, 14-Mar-03, to lugnet.cad.dev)
|
| | | | | |
| | | | | | | Re: Calling all Meta-commands —Kevin Clague
|
| | | | | | | I don't think of any new meta-commands as polution. Possibly over-population? I've got mixed feelings about the LTrax solution. It is very hard to know which meta-commands will be usable across many applications. Certainly the original LDraw (...) (22 years ago, 14-Mar-03, to lugnet.cad.dev)
|
| | | | | | | |
| | | | | | | | | Re: Calling all Meta-commands —Larry Pieniazek
|
| | | | | | | | (...) Namespace Pollution is a technical term. It's not meant as an insult, mind you. It refers to a common phenomena in programming, in which things become hard to use because of scope problems, because things named in global scope interfere with (...) (22 years ago, 14-Mar-03, to lugnet.cad.dev)
|
| | | | | | | | |
| | | | | | | | | | Re: Calling all Meta-commands —Tim Courtney
|
| | | | | | | | In lugnet.cad.dev, Larry Pieniazek writes: [...] (...) I agree with the route of a standards body to control (officially adopted) meta-commands. The second option is just a fix, and the third option is unacceptable, especially if we want to see more (...) (22 years ago, 14-Mar-03, to lugnet.cad.dev)
|
| | | | | | | | |
| | | | | | | Re: Calling all Meta-commands —Kyle McDonald
|
| | | | | | | (...) I think that, with a little investigation, each command might be identified as 'general purpose' or 'application specific.' I think that haveing the app-specific ones prefixed with the appname (or even 'APP {appname}') isn't such a bad idea. (...) (22 years ago, 14-Mar-03, to lugnet.cad.dev)
|
| | | | | | | |
| | | | | | | | | Re: Calling all Meta-commands —Kevin Clague
|
| | | | | | | | | Kyle, This seems very pragmatic solution. I like it because there does not seem to be a "one size fits all" solution. Kevin (...) (22 years ago, 14-Mar-03, to lugnet.cad.dev)
|
| | | | | | | | | |
| | | | | | | | | Re: Calling all Meta-commands —Kevin Clague
|
| | | | | | | | In thinking about this a bit more, I flashed on a quote from Yoda in one of the Star Wars movies "Hard to see the future is".... I've added some meta-commands to the name space that are certainly specific to LPub and the creation of building (...) (22 years ago, 14-Mar-03, to lugnet.cad.dev)
|
| | | | | | | | |
| | | | | | | | | | Re: Calling all Meta-commands —Kyle McDonald
|
| | | | | | | | (...) Ain't that the truth! (...) This is kinda what I was proposing. If you had known that the APP {appname} branch of the namespace was open for any developer to use as he saw fit, but that other commands needed more community buy in, you probably (...) (22 years ago, 14-Mar-03, to lugnet.cad.dev)
|
| | | | | | | | |
| | | | | | | Re: Calling all Meta-commands —Tore Eriksson
|
| | | | | | | (...) If you write FooCad, don't regard LTrax as a program, but rather a family of standard meta-commands. But as the "owner" of that family, I may change the spec's and thus make FooCAD incompatible... When it comes to LTrax - I know you most (...) (22 years ago, 14-Mar-03, to lugnet.cad.dev)
|
| | | | | | | |
| | | | | | | Re: Calling all Meta-commands —Larry Pieniazek
|
| | | | | | | (...) Neither. You should PUBLICLY support the command and make it known that you are doing so. (...) maybe. (22 years ago, 14-Mar-03, to lugnet.cad.dev)
|
| | | | | | | |
| | | | | | | Re: Calling all Meta-commands —Steve Bliss
|
| | | | | | (...) 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)
|
| | | | | | |
| | | | | Re: Calling all Meta-commands —Paul Gyugyi
|
| | | | | One approach to namespace management is to have format the commands like so: 0 MODULENAME COMMAND blah Authors would ask for a unique MODULENAME string to use, and prefix that in front of any "experimental" commands. For example, say I want to (...) (22 years ago, 18-Mar-03, to lugnet.cad.dev)
|
| | | | | |
| | | | | | | Re: Calling all Meta-commands —Kevin Clague
|
| | | | | | (...) This is the approach that Michael Lachman on MLCAD. In an email, where he gave us permission to include his meta-command descriptions in our LDraw specification (yay!) he indicated that he has started to use MLCAD as his module name for all (...) (22 years ago, 19-Mar-03, to lugnet.cad.dev)
|
| | | | | | |
| | | | | Re: Calling all Meta-commands —Steve Bliss
|
| | | | (...) 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)
|
| | | | |
