LEGO SYSTEM Trains : 626


Trains / 626	625 \| 627

Subject:	Re: LDraw and the Track Designer (Was: Next show)
Newsgroups:	lugnet.trains, lugnet.cad.dev
Date:	Tue, 16 Feb 1999 17:25:29 GMT
Viewed:	1622 times

This sounds like an excellent idea, however I'm not sure how to implement it. If it were a built in feature of Track Designer it would require that the entire rendering engine of LDraw be built into TD. A bit daunting! If it were built into LDraw, LDraw would have to understand the TD file format for registry files. Again, a bit daunting. If it were a stand-alone utility it would have to have the LDraw engine plus TD file format knowledge. My preference would be the 3rd option, although a sligthly more off-the-wall idea might be a hybrid approach. LDraw, LDLite or whatever would have an export feature that allowed you to export views in some to-be-determined file format. TD would then be able to import this format and convert it to its internal format. Matt

Message has 1 Reply:

		Re: LDraw and the Track Designer (Was: Next show)
(...) A stand-alone utility could call LDraw (or LDLite) to produce the images, but extract the (port) information directly from the .DAT file. Calling into LDraw/LDLite is pretty easy -- both programs are command-line driven. The utility would have (...) (26 years ago, 16-Feb-99, to lugnet.trains, lugnet.cad.dev)

Message is in Reply To:

		Re: LDraw and the Track Designer (Was: Next show)
(...) Shouldn't give any problems. (...) If we just register the port information for the relevant parts (road plates, track, and monorail track), and inline all sub-files (not including parts) the inlined version of the model will contain indirect (...) (26 years ago, 16-Feb-99, to lugnet.trains, lugnet.cad.dev)

17 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