To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cadOpen lugnet.cad in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / 9843
9842  |  9844
Subject: 
Re: Lego XML?
Newsgroups: 
lugnet.cad
Date: 
Wed, 30 Apr 2003 03:40:13 GMT
Viewed: 
934 times
  
In lugnet.cad, Amy Hughes writes:
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 things for the sake of showmanship.

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 LDraw file format can do, plus more.

The practical capabilities that a BrickML would add include:

- The ability to convert a part to both LDraw's .ldr file format and to
POV-Ray's .inc file format -- from the same master part specification.
BrickML could include, for example, a cylinder primative which could be
output at a POV-Ray cylinder object or as a set of LDraw triangles
approximating a cylinder.  It could include a color specifier which would
output as the appropriate RGB color for POV-Ray or as the appropriate LDraw
color for LDraw.  It could be a really nice way to unite LDraw, POV-Ray, and
other 3D systems.

- Ease of including meta-data and outputting it as LDraw or POV-Ray comments.

- Possibly easier to validate syntax than .ldr for new tools.  (This is
marginal, though.)

The big win would be native suport for things like cylinders, spheres,
cones, meshes, and textures.  And it could do CSG.  A conversion to .ldr or
.pov would be accomplished by using whatever primatives were available, so
that the result would be of the highest quality.

--Todd



Message has 1 Reply:
  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)

Message is in Reply To:
  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)

16 Messages in This Thread:







Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR