 | | Re: Need to assign part numbers - Rotary Dial Slope Brick
|
|
(...) (URL)and (...) (URL)Also, some of the inventories in Peeron mention a tile with "thick 3" (...) (URL)or yet another pattern. (...) OK - I'll assign p01 thru p04 for the thin black figures, as in set 6395. You're right, there is a thick "3", (...) (22 years ago, 14-Mar-03, to lugnet.cad.dat.parts)
|
| |
| | Re: Latest BFC Spec?
|
|
(...) Thanks, Orion! Would you mind emailing me the plain text, so I can assemble it on a web page for LDraw.org? We can also host the PDF you created on the server for those who prefer it in that format. -Tim (22 years ago, 14-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Latest BFC Spec?
|
|
(...) OK I'm done. Here's the spec in a more readable format: (URL) didn't change anything, I just cleaned up the text and made a TOC. (22 years ago, 14-Mar-03, to lugnet.cad.dev)
|
| |
| | 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: Need to assign part numbers - Rotary Dial Slope Brick
|
|
(...) (URL) some of the inventories in Peeron mention a tile with "thick 3" pattern---I have no idea if that's 3070bp03 (URL) yet another pattern. -- TWS Garrison (URL) capital letters in address for direct reply. (22 years ago, 14-Mar-03, to lugnet.cad.dat.parts)
|
| |
| | Re: Need to assign part numbers - Rotary Dial Slope Brick
|
|
(...) Welcome. (...) No - there is currently no linkage between the peeron pattern numbers (which just start with x1 and increment) and the official LDraw pattern numbers which we try to categorise. So please do use 30363ps1. (...) Yes - this is as (...) (22 years ago, 14-Mar-03, to lugnet.cad.dat.parts)
|
| |
| | 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)
|
