 | | Re: General Comments to MLCad
|
|
(...) Could you avoid writing out the file as a ".DAT" file extension if you are making extensions to the long established LDraw DAT file format? This would clear up confusion right away and avoid further incompatibility issues if other LDraw-clone (...) (25 years ago, 19-Dec-99, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | Re: General Comments to MLCad
|
|
(...) It would be better (IMO) to format non-LDraw information as LDraw-style meta-commands, and keep everything in the DAT format. That gives the file the widest transportability between programs. Steve (25 years ago, 20-Dec-99, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | Re: General Comments to MLCad
|
|
(...) Ahh, "tagged" information then, in other words? :) Cool....... --Todd (25 years ago, 20-Dec-99, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | Re: General Comments to MLCad
|
|
(...) Yep. LDLite does things like 0 COLOR <color definition information> along with other stuff, and the HTML instruction generator in LDAO recognizes a subassembly statement: 0 SUB <file> <layout options> and in lugnet.cad.dev, we're proposing to (...) (25 years ago, 21-Dec-99, to lugnet.cad.mlcad, lugnet.cad.dev)
|
