 | | June MOTM/SOTM Update
|
|
Due to my work schedule and my visit to California for my brother's high school graduation, I couldn't find the time to properly setup the June MOTM/SOTM. Instead of doing a shoddy job, I'm going to cancel the June contests. I apologize for this and (...) (20 years ago, 15-Jun-04, to lugnet.cad, lugnet.cad.dev.org.ldraw)
|
| |
| | LDBoxer - Next Step and My Datsville Plans
|
|
So far, LDBoxer has replaced all bricks and plates that has both top studs and bottom studs/tubes covered by non-transparent parts. Next step is to eliminiate drawing bottom studs/tubes when only top studs are visible, and vice versa. Many models (...) (20 years ago, 15-Jun-04, to lugnet.cad.dev)
|
| |
| | Re: License Intent
|
|
(...) I don't know. I think when something is statically linked you can recover the original code with a disassembler. It's really still there in a different form. There's no way to disassemble a picture into the ldraw code without using the ldraw (...) (20 years ago, 13-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
Just for the record: IANAL (...) Mine. LDraw files are source code (at least according to the definition in the LGPL). And unless you consider rendering a specific kind of compilation, LGPL would not allow you to do anything useful with a parts (...) (20 years ago, 12-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) [snip] (...) I read the exact same clause and come to exactly the opposite conclusion. My reasoning is that because linking is something you do to code, not LDraw parts; the clause has no bearing to LDraw parts. Is my interpretation right, or (...) (20 years ago, 12-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) From (URL): »However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable (...) (20 years ago, 12-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Questions On ldconfig.ldr (Was: colours.txt -> LDraw-org Official Part Updates!)
|
|
(...) Well the spec is changing so these commands will go away. We (the LSC) are working to get the spec for the color definitions (the !COLOR Meta coomand) finalize by the next parts release. (...) LDView currently uses this file and once we (...) (20 years ago, 11-Jun-04, to lugnet.cad.dev)
|
| |
| | Questions On ldconfig.ldr (Was: colours.txt -> LDraw-org Official Part Updates!)
|
|
(...) Oh boy, I've never noticed that one! Must be because of its misleading name and extension. So, what does the A, DR, DG, DB, DA columns stand for? (A is always = 255, so one can wonder what good it does.) It should benifit from some more (...) (20 years ago, 11-Jun-04, to lugnet.cad.dev)
|
| |
| | Re: colours.txt -> LDraw-org Official Part Updates!
|
|
(...) This is what the ldconfig.ldr file is. Look for it the LDraw base dir. -Orion (20 years ago, 11-Jun-04, to lugnet.cad.dev)
|
| |
| | colours.txt -> LDraw-org Official Part Updates!
|
|
(...) Sorry, I just can't find it. Could you give me a direct link? Thanks, /Tore (btw, the file colours.txt is very close to what I have in mind, only that what I think of should not be limited to 80 colours, it should be stored in the LDraw (...) (20 years ago, 11-Jun-04, to lugnet.cad.dev)
|
