 | | Re: Lego XML? —Kyle McDonald
|
| | | (...) I know VRML was mentioned earlier, and now XML. Someone may want to look at X3D (I think that's what it's called.) It is a newer relative of VRML for 3D graphics done in XML. I haven't looked at it myself, but I hear about it all the time on (...) (22 years ago, 29-Apr-03, to lugnet.cad)
|
| | | |
| | | | | 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)
|
| | | | | | |
| | | | | Re: Lego XML? —Amy Hughes
|
| | | | (...) Is there a problem that any of these technologies will solve, or any new practical capabilities that they will add, or is this another exercise in geek supremacy? :-) I'm hopeful that the file format committee won't unnecessarily complicate (...) (22 years ago, 30-Apr-03, to lugnet.cad)
|
| | | | |
| | | | | | Re: Lego XML? — Todd Lehman
|
| | | | (...) I can't speak for the others who are excited about the possibility of creating a BrickML, but to me it kind of seems like a logical successor to the LDraw file format, given that it could handle meta-data elegantly and do everything that the (...) (22 years ago, 30-Apr-03, to lugnet.cad)
|
| | | | |
| | | | | | Re: Lego XML? —Cary Clark
|
| | | | (...) ... (...) Let me expand on that. An XML color can be an abstraction that is defined somewhere else. So the attribute color="red" can mean LEGO red in the LEGO namespace, but some other red (like 0xFF0000) in the XHTML namespace, for instance. (...) (22 years ago, 30-Apr-03, to lugnet.cad)
|
| | | | |
| | | | | | Re: Lego XML? —Gustavo Patow
|
| | | | | Hi: Let me add my two cents: As I hope you ALL know :-), I'm working with a student of mine in a new verison of LeoCAD called LeoCAM, which main feature is the ability to connect parts by their connectors (like axles, axle-holes, stud,stud-inles). (...) (22 years ago, 30-Apr-03, to lugnet.cad)
|
| | | | | |
| | | | | | Re: Lego XML? —Leonardo Zide
|
| | | | (...) Color is a bad concept when you're making parts, it would be much better to have a material library instead. For example, currently we use the same black color to describe tires, the reflective sides of bricks and the non-smooth sides of (...) (22 years ago, 30-Apr-03, to lugnet.cad)
|
| | | | |
