 | | Re: Calling all Meta-commands
|
|
Having read through this thread, I've seen a lot of good points made. However, it also appears that people haven't really fully thought about the implications of meta-commands. It's very important to realize that meta-commands are presented as (...) (22 years ago, 14-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) 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
|
|
I have invented a 'general purpose' header statement, 'Parent:' that points to the parent[s] of a model file. See example below. I find it very useful when sorting out Datsville submodels, and also in animations. I also use the 'Was:' statement for (...) (22 years ago, 14-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) 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
|
|
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)
|
