 | | Re: Using MPD syntax in official part files —Joshua Delahunty
|
| | | (...) 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 —Travis Cobbs
|
| | | | (...) 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 —Steve Bliss
|
| | | | | (...) Yeah, what he said. (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts, FTX)
|
| | | | | |
| | | | | | Re: Using MPD syntax in official part files —Joshua Delahunty
|
| | | | (...) 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)
|
| | | | |
