 | | Re: Lego XML? —Gary Thomas
| | | | (...) Well actually I was thinking more along the lines of describing a model in terms of it's parts, but not a full 3d description like X3D. Something like this (sorry, this looks terrible without a monospaced font): <?xml version="1.0" (...) (22 years ago, 29-Apr-03, to lugnet.cad)
| | | | | | | | | | Re: Lego XML? —Kyle McDonald
| | | | | | (...) Looked fine to me. I only use a monospace font. :) (...) I see. I know nothing about X3D, but I imagined a model might be something like you describe. However, theoretically the part files the model referenced could (I think?) be coded in (...) (22 years ago, 29-Apr-03, to lugnet.cad)
| | | | | | | | | | | | Re: Lego XML? — Todd Lehman
| | | | | (...) 1 0 0 0 1)"/> (...) Wow, that is pretty cool. A person could write a 20-line Perl program to transmogrify that into .ldr format pretty easily, and vice-versa. (...) Waycool. BTW, how do people feel about specifying colors in hex RGB format? (...) (22 years ago, 30-Apr-03, to lugnet.cad)
| | | | | | | | | | | | Re: Lego XML? —Steve Bliss
| | | | | (...) I've thought about this, because most LDraw-programs (ie, LDLite, L3Lab, MLCAD, L3P, ldglite, LDView?) provide a way to code color-values directly in some RGB method. My issue is that different systems (computer systems, graphics systems) (...) (22 years ago, 1-May-03, to lugnet.cad)
| | | | | | |
