Subject:
|
Re: Using MPD syntax in official part files
|
Newsgroups:
|
lugnet.cad.dat.parts
|
Date:
|
Thu, 11 Feb 2010 05:46:52 GMT
|
Viewed:
|
19501 times
|
| |
|
|
In lugnet.cad.dat.parts, Travis Cobbs wrote:
| |
First of all, let me say that while my previous post probably implied that
I’m against allowing MPDs as parts, I am in fact still open to the
possibility. I’m just not sure I’m completely convinced by the arguments
given so far.
|
I think this is a good one:
MPD parts would be a great way to store “default” textures for texture mapping
(hex encode them). That would encapsulate the design with the part, overcoming
one of the big “pain points” of adopting textures. Textures could still be
overridden in supporting software through use of an external “hi-res” directory
in the LDRAW search path.
I CAN think of a few issues (but why announce THOSE, right? :)), but it’s
another aspect that might make the idea an acceptable one.
-- joshuaD
|
|
Message has 1 Reply:
 | | Re: Using MPD syntax in official part files
|
| (...) I really don't like this idea. I agree that it has the cool property of encapsulating everything in one file, but it has three big problems that I can think of off the top of my head: "Hex" encoding of the texture file increases its size by a (...) (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts, FTX)
|
Message is in Reply To:
| | Re: Using MPD syntax in official part files
|
| First of all, let me say that while my previous post probably implied that I'm against allowing MPDs as parts, I am in fact still open to the possibility. I'm just not sure I'm completely convinced by the arguments given so far. (...) The only place (...) (15 years ago, 10-Feb-10, to lugnet.cad.dat.parts, FTX)
|
68 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
|
|
|
|
