| | Re: A comprehensive LDraw object model
|
|
(...) A couple of different approaches to this have been discussed before. I think the most generic solution was to implement a 0 DETAIL <level> meta-command, that would identify the detail-level of the following lines. A 0 detail level indicates (...) (23 years ago, 11-Feb-02, to lugnet.cad.dev)
|
|
| | Re: A comprehensive LDraw object model
|
|
"Sproaticus" <jsproat@io.com> schrieb im Newsbeitrag news:GrBy72.EJI@lugnet.com... (...) Conclusion: The LineType-classes are wrapper classes for the lines in the dat files. Simple in- and output methods are included, also simple transforming (...) (23 years ago, 11-Feb-02, to lugnet.cad.dev)
|
|
| | Re: need help w/ name (set #4817)
|
|
(...) So, unless someone else chimes in, it looks like these will be the names: 970p4b Minifig Hips with Leather Belt/Straps Pattern 971p4b Minifig Leg Right with Leather Belt/Straps Pattern 972p4b Minifig Leg Left with Leather Belt/Straps Pattern (...) (23 years ago, 11-Feb-02, to lugnet.cad.dev)
|
|
| | Minifig Hair Female
|
|
Since the last official parts update, I have relished the ability to put hair on my male minifigures. I humbly request that if anyone would be willing/able, that he would make some Minifig Hair Female. Best regards to all, and thanks. --Ryan (23 years ago, 11-Feb-02, to lugnet.cad.dev)
|
|
| | Re: A comprehensive LDraw object model
|
|
(...) Yes, What you're describing does sound like BFC to me. As someone else (travis I think?) said, BFC is a useful optimiziation for reducing the number of surfaces that need to be drawn. But it's not the same thing I was talking about. BFC (...) (23 years ago, 11-Feb-02, to lugnet.cad.dev)
|
|
| | Re: A comprehensive LDraw object model
|
|
(...) Ok. Up until now I've been under the impression we were trying to come up with a pure interface definition, independent of any particular language, platform, or implementation. When I asked if they weren't all abstract, I was envisioning (...) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
|
| | Re: A comprehensive LDraw object model
|
|
(...) I can definately see the benefits of a standard library interface. Even an implementation might have a lot of uses. I just think that you will get the best design for the interface, if you forget about how you or anyone implemented it in the (...) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
|
| | Re: A comprehensive LDraw object model
|
|
(...) Backface culling (BFC) is what you are describing, but it isn't what Kyle was asking for :-). In traditional realtime 3D rendering, polygons only have one side. The back side is literally non-existent. It doesn't get drawn at all. This is (...) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
|
| | Re: A comprehensive LDraw object model
|
|
(...) Well, while I haven't tried it, I'm fairly sure that my implementation of MPD-handling in LDView would happily load an MPD file as a subfile of another MPD file or a dat file. :-) --Travis Cobbs (tcobbs@REMOVE.halibut.com) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
|
| | Re: A comprehensive LDraw object model
|
|
(...) The way I designed my stuff is that the code in the linetype classes manage the objects they contain -- mostly just allocation, serialization and stringification of a matrix or a list of vectors. However, any rendering or parsing behavior is (...) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|