 | | 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)
|
| |
| | Re: Using MPD syntax in official part files
|
|
(...) Absolutely. I wasn't advocating sticking 'public' subparts into the part's MPD. Just to be clear. Steve (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Using MPD syntax in official part files
|
|
(...) You know, it occurs to me that if MPD's were allowed as parts, it would be a GREAT place to put a texture file (properly hex encoded, no doubt). They're almost always single-part-only. And if one wanted better textures than "come standard?" (...) (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Using MPD syntax in official part files
|
|
(...) 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. (...) (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts, FTX)
|
| |
| | 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)
|
| |
| | Re: Using MPD syntax in official part files
|
|
(...) Yeah, what he said. (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Using MPD syntax in official part files
|
|
(...) In lugnet.cad.dat.parts, Joshua Delahunty wrote: (...) In lugnet.cad.dat.parts, Travis Cobbs wrote: (...) I was actually thinking "uuencode" when I wrote this, and used hex for shorthand and because I figured it was more universally (...) (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts, FTX)
|
