|
 | | Re: LDraw color conversions
|
| (...) Tore, Is this the kind of output you are looking for? (URL) link will probably wrap) That's just some of the info from my Color Tree pages: (URL) me know what you need, or how you need it presented. I'd be glad to help in any way I can. HTH, (...) (20 years ago, 16-Jun-04, to lugnet.cad.dev)
| |
|  
ldraw
(score: 0.357)
|
|
| | Re: Variants of 4.5v train motors
|
| (...) The actual motors (both 12V and 4.5V) were sold seperately as replacement packs, so users can screw open the case and replace the motor (either replacing a broken motor or replace a 4.5V motor with a 12V motor or vice versa). (URL) 12V (peeron (...) (20 years ago, 29-Jun-04, to lugnet.cad.dev, FTX)
| |
|
ldraw
(score: 0.357)
|
|
| | Re: Variants of 4.5v train motors
|
| (...) I have checked my collection of train motors (which has reached an amount of 9), including all three mentioned variants. (Please note that I have changed the order of the quoted lists from Chris' message) (...) Got this one in blue, with a (...) (20 years ago, 27-Jun-04, to lugnet.cad.dev)
| |
|
ldraw
(score: 0.357)
|
|
| |
|
ldraw
(score: 0.356)
|
|
| | 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)
| |
|
ldraw
(score: 0.356)
|
|
| | Re: Primitive Generator program update
|
| (...) Just for the record, this is set out in the BFC standard, (URL). In the section "Parts Library Guidelines", it is stated: (...) Interesting side note: this section also says: (...) Which means we should be slapping 0 BFC NOCERTIFY tags on all (...) (20 years ago, 21-Jun-04, to lugnet.cad.dev)
| |
|
ldraw
(score: 0.356)
|
|
| | 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)
| |
|
ldraw
(score: 0.356)
|
|
| | Re: Questions On ldconfig.ldr (Was: colours.txt -> LDraw-org Official Part Updates!)
|
| (...) A = alpha (transparency) DR, DG, DB, DA = dithered RGB,A. If RGB = D(RGB), then the color is solid. If DA=0, the color is transparent. Otherwise, the color is dithered and/or translucent. (...) Actually, that kind of information should be set (...) (20 years ago, 16-Jun-04, to lugnet.cad.dev)
| |
|
ldraw
(score: 0.356)
|
|
| |
|
ldraw
(score: 0.356)
|
|
| | 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)
| |
|
ldraw
(score: 0.356)
|
|
| | Re: License Intent
|
| (...) The spirit of what I'm trying to get at is this: if someone wants to read LDraw into a proprietary format, shouldn't they also write LDraw? Taking an open format and importing it into a closed format, without a way to write back to the open (...) (20 years ago, 9-Jun-04, to lugnet.cad.dev.org.ldraw)
| |
|
ldraw
(score: 0.356)
|
|
| | 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)
| |
|
ldraw
(score: 0.356)
|
|
| |
|
ldraw
(score: 0.356)
|
|
| | Re: License Intent
|
| (...) I want to address just this point for now. I don't see how ensuring the Parts Library is open would prevent Larry (or anyone else) from distrbuting a LDraw file commercially. Due to the nature of the LDraw file system, I would not consider an (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
| |
|
ldraw
(score: 0.355)
|
|
| |
|
ldraw
(score: 0.355)
|
|
| | Licenses... some background
|
| Longtime fans of the LDraw format and the LDraw system of tools know that this current discussion around licensing is by far NOT the first time the topic came up. The discussion is currently sort of disjointed in my personal view (and that of (...) (20 years ago, 20-May-04, to lugnet.cad.dev.org.ldraw) !
| |
|
ldraw
(score: 0.355)
|
|
| | Re: License Intent
|
| (...) I am not sure I mind allowing SteerCo/LDraw.org to relicense my parts under a different license, but I definitely don't want to give SteerCo/LDraw.org any special rights. That would also be a violation of point 5 in The Open Source Definition (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
| |
|
ldraw
(score: 0.355)
|
|
| | Re: License Intent
|
| (...) From my recollection (and this is digging back, you made me think here) I went off of the LDraw.exe LICENSE.TXT. The clause I presumed gave permission to publish commercially was: -- USAGE PROVISIONS: Permission is granted to the user to use (...) (20 years ago, 10-Jun-04, to lugnet.cad.dev.org.ldraw)
| |
|
ldraw
(score: 0.355)
|
|
| | Re: License Intent
|
| (...) If anybody has copyright to a _part_, it must by default be LEGO. But the copyright to a rendering of a part in one or a number of LDraw files is held jointly by all the involved parties (ignoring the difficult question of exactly how small (...) (20 years ago, 10-Jun-04, to lugnet.cad.dev.org.ldraw)
| |
|
ldraw
(score: 0.355)
|
|
| |
|
ldraw
(score: 0.355)
|
