 | | Re: ldglite (ldlite for OpenGL and Linux) new stuff
|
|
(...) You can keep compatibility with the POV libraries but each one (LGEO, L3P and Anton Rave's (?)) use a different coordinate system. LeoCAD uses the parts from LGEO first and then if something is missing, it creates the parts using its own (...) (25 years ago, 3-Feb-00, to lugnet.cad.dev)
|
| |
| | Re: ldglite (ldlite for OpenGL and Linux) new stuff
|
|
(...) Yes, I totally agree with you. I think that once you bother to learn the LEdit keycodes, it is much quicker to use than a "point and click" CAD system. I think that any new LDraw-based CAD system should also imlement the LEdit kecodes for the (...) (25 years ago, 3-Feb-00, to lugnet.cad.dev)
|
| |
| | Re: ldglite (ldlite for OpenGL and Linux) new stuff
|
|
(...) A feature I already started adding to ldglite is to take ldraw commands from stdin if no filename is present on the commandline. I think this lends itself better to external control than polling a file. This is of course based on my completely (...) (25 years ago, 3-Feb-00, to lugnet.cad.dev)
|
| |
| | Re: ldglite (ldlite for OpenGL and Linux) new stuff
|
|
(...) Well, excuse my ignorance, but I couldn't find the source at (URL) (25 years ago, 3-Feb-00, to lugnet.cad.dev)
|
| |
| | Re: ldglite (ldlite for OpenGL and Linux) new stuff
|
|
(...) What about the parts libraries used by the Ray tracing folks? Or is a totally new format in order? Either way I think the right thing to do is start with some utilities that convert the LDRAW formatted parts to whatever form we want to use. (...) (25 years ago, 3-Feb-00, to lugnet.cad.dev)
|
