 | | 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)
|
| |
| | Re: A comprehensive LDraw object model
|
|
(...) Well, this raises the point: what ideal is the LDraw format aiming for? I don't think it's really going anywhere; any real change to the format would break compatability with the legacy LDRAW.EXE. I'm proposing a class library for the existing (...) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
| |
| | Re: Category for segments parts
|
|
Carsten wrote: CS> .... CS> For example it would be nice to have ML-Cad known that a special pat is a CS> segment part and when you drop it in the model window it woul ask right away CS> where to set start and end-point and calculate the segment (...) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
| |
| | Re: A comprehensive LDraw object model
|
|
(...) Standard libraries/classes for reading, writing and processing LDraw and MPD files is certainly a good idea, but I am not certain rendering functions should be a part of such a library although it is an obvious extension. Jacob (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
| |
| | Category for segments parts
|
|
Hello! Past few days when i was working up parts who never have been reviewed before in parts tracker I noticed a lot of segment parts for Lego Technic. Basically these parts consists of a small segment or link to make a wire or tube of it (...) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
| |
| | Re: A comprehensive LDraw object model
|
|
"Sproaticus" <jsproat@io.com> schrieb im Newsbeitrag news:GrA7CA.24y@lugnet.com... (...) Shall this lines be only container classes or shall they have the working code? If they have working code, they are heavily depending on the target system (...) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
| |
| | Re: A comprehensive LDraw object model
|
|
(...) <snip> First, this is a nifty idea. Objectifying this is long overdue. But I was struck wondering, is this trying to objectify the current dat format as it is, or an ideal one as we would like to see it be... Also, are you a fan of the MVC (...) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
| |
| | Re: A comprehensive LDraw object model
|
|
(...) IIRC (and I wish I could find the reference) the LDraw spec does support this. It depends on the order of the points in the polygon; e.g. clockwise points out, counterclockwise points in. Or something like that. But last I heard of this, there (...) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
| |
| | Re: A comprehensive LDraw object model
|
|
(...) I'll have a better answer for this when I port my Java implementation to Perl. But yah, I guess "comprehensive" and "generic" don't quite mix well. I want comprehensive, in that this library could be used for many different methods of (...) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
| |
| | Re: A comprehensive LDraw object model
|
|
I like this. I don't think I can contribute that much. I would like to though. I have been working in Java with my animation program ((URL) and I can contribute a class for LineType1. Most useful is a rotation function that I would like to think is (...) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
| |
| | Re: A comprehensive LDraw object model
|
|
(...) The base class is abstract, the ones not marked "abstract" aren't. This class hierarchy is actually the class library I whipped up over the past week. About 95% of what I posted here has working code, but I didn't want to push any of that if (...) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
| |
| | Re: A comprehensive LDraw object model
|
|
(...) Actually this brings up a different issue. I haven't put alot of thought into it yet, but I think it would be useful to add information in the part files that would allow a program to differentiate between geometry that represents 'outside' (...) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
| |
| | Re: A comprehensive LDraw object model
|
|
How about an LDraw DAT model reducer - something that hacks out the insides and leaves nothing but a hollow shell? This way you could port it to platforms that can't handle so many polygons, and also render in realtime. It would kind of be like (...) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
| |
| | Re: A comprehensive LDraw object model
|
|
(...) Aren't all of these classes Abstract? I mean this is only a template for implementing a Class Library right? Are you planning on actually filling in the code also? or just defining the interfaces? (...) So far you've got a few more levels in (...) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
| |
| | Re: A comprehensive LDraw object model
|
|
(...) > (Maybe not too much, let's keep it lean and mean.) At the least, I > think we should make the object model workable in C++, Java, Perl and > Python. (...) This is interesting. I wonder what we can do as far as making it both comprehensive (...) (23 years ago, 10-Feb-02, to lugnet.cad.dev)
|
| |
| | Re: A comprehensive LDraw object model
|
|
(...) Here's my first contribution, a rough outline of a class structure. *** LDRAW LINE TYPE CLASSES *** abstract class LineType - ancestor class for all line-type objects + class LineType0 - comment line-type + class LineTypeCommand - command (...) (23 years ago, 9-Feb-02, to lugnet.cad.dev)
|
