 | | Re: Looking for part - numbers confused
|
|
Ok thanks for the help guys. Maybe I should attempt drawing the part myself or recreate 6057.dat to fit my needs? :) Jos (...) (22 years ago, 15-Mar-03, to lugnet.cad.dat.parts)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) Don't forget about LDLite: (URL) (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
In lugnet.cad.dev, Kevin Clague writes: Mucho Snippo. (...) Excellent points, Kevin! All - I can second everything Kevin is saying here. Through many private exchanges, and by meeting Kevin at BricksWest, I've come to understand his position on this (...) (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Looking for part - numbers confused
|
|
Jos Henckens <jos.henckens@nephilimco.com> schrieb im Newsbeitrag news:m2047vo7vu2v91l...4ax.com... (...) The name "Bar .. Tapered" is "Boat Rigging .." in the parts-list. Only the smaller one is an official part. I'm not sure if the larger one has (...) (22 years ago, 15-Mar-03, to lugnet.cad.dat.parts)
|
| |
| | Re: Calling all Meta-commands
|
|
Hi All, Wow! This thread has created more postings that I thought it would. So far I've gathered meta-commands from (URL) Eriksson LTrax, Parent: Kevin Clague - LPub and LSynth There must be more. If you know of programs that define their own (...) (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Looking for part - numbers confused
|
|
(...) Only found the smaller version of this, part number 6057.dat. Should be under other parts, b in mlcad. (22 years ago, 15-Mar-03, to lugnet.cad.dat.parts)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Hi Orion, Here is my take on the current state of LDraw related tools and parts library. There are a few documents that sketch out the basic mechanics of what we use today, but the real standards are the programs that we have that use them. We (...) (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Looking for part - numbers confused
|
|
Hello I'm looking for following part as described on (URL) : 2541 Brown Bar 5 x 28 Tapered I can't find it between the updates (both official and unofficial )at ldraw.org. Looking this number up at lugnet.com led me to some minifig parts? The part (...) (22 years ago, 14-Mar-03, to lugnet.cad.dat.parts)
|
| |
| | LPub and disproportionate Parts List Images?
|
|
I just rendered a set of instructions in LPub at screen resolution, 800x600. LPub rendered the parts list images at what seems to be print resolution. Previously when I generated instructions for the same model, LPub rendered them proportionate to (...) (22 years ago, 15-Mar-03, to lugnet.cad)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Cool. Kevin started the call for meta-commands, and I believe he plans to assemble them into a list/document. If you want to help with that, I suggest you email him. -Tim (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Consider this my volunteer for this standards body. I can also work on an informal list of META commands. -Orion (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) While a noble proposal in spirit, I strongly feel we need to organize what we have before taking that radical of a step forward. Once we've defined the current LDraw format spec and all meta-commands, a standards body can work at defining a (...) (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) I agree the backward compatibility is good, to a point. This is especially true for the parts library. Too many times we refuse to fix something or extend the file spec (e.g. new colors not able to be represented by existing color numbers) (...) (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) Why not keep previous meta-commands where they're at, but also introduce a new line-type exclusively for meta-commands? I'm not too keen on MLCad's WRITE, to me it makes little to no sense. Maybe if it was COMMENT or even ! (like an HTML (...) (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) Why not force comments to be a meta-command like MLcad does with WRITE? Then the only problem you have is new files created with Ledit, and old files which will need to be converted. And Ldraw would still handle them OK. ROSCO (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) Yes. (...) I think we'll see coming out of this discussion something that will prevent the meta-command chaos we've seen for the past years. No one here is talking about a new file format, or new version of a spec - yet. First we need to fully (...) (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) Are we REALLY stuck with current meta-commands? Sure if we change them all (the META Statements) after setting up a "body of standards" our old files may not work but somewhere down the future is it NOT better to NOT worry about backward (...) (22 years ago, 15-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
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
|
|
(...) Kevin & Travis - These are very good points. As a non-programmer, but someone who has a general knowledge of the LDraw file format, I think it is a good idea to separate comments from meta-commands. Also, talk of a standards body is a good (...) (22 years ago, 14-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Latest BFC Spec?
|
|
(...) Sure, but give me a moment. I just noticed the the graphic I added to the text didn't make it into the PDF therefore skewing the TOC. -Orion (22 years ago, 14-Mar-03, to lugnet.cad.dev)
|
