 | | Re: Lego XML?
|
| (...) 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 (...) (21 years ago, 30-Apr-03, to lugnet.cad)
| | | | | Re: Lego XML?
|
| (...) 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 (...) (21 years ago, 30-Apr-03, to lugnet.cad)
| | | | | Re: Lego XML?
|
| (...) ... (...) 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. (...) (21 years ago, 30-Apr-03, to lugnet.cad)
| | | | | Re: Lego XML?
|
| 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). (...) (21 years ago, 30-Apr-03, to lugnet.cad)
| | | | | Re: Lego XML?
|
| (...) 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 (...) (21 years ago, 30-Apr-03, to lugnet.cad)
| |
