 | | 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)
|
