 | | Re: Color Defining Systems Summary?
|
|
(...) The LSC is almost done with the !COLOR meta-statement that should satisfy your need once L3P and MLCad support it. You can read the current draft here: (URL) (20 years ago, 4-Jun-04, to lugnet.cad.dev)
|
| |
| | Color Defining Systems Summary?
|
|
I think that there are a number of different systems for defining new or custom colors in the large number of LCad programs, right? Most of them are considerate towards original LDraw and other tools that are not supporting that system. But I think (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev)
|
| |
| | Re: License Intent
|
|
I think that we shouldnt say "you cant distribute the library and charge for it" but instead do what e.g. GPL does and allow selling it but with the licence (which includes the right to freely redistribute the covered works) applying to it (so if I (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) While I wouldn't like that, I'm not sure we really need to prevent it. OS software seems to do ok with allowing people to profit - the assumption is that if you use the code to profit, you'll probably make improvents to it, which (under OS (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) Would it work if the license says that any future changes need author approval, but have a timeout? If after, say, 30 days of asking for approval (on ldraw, lugnet, and in email) there's no responce, the approval is assumed? Maybe 30 days is (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) Actually, redhat stopped shipping free linux (with the exception of Fedora, which isn't supported by Redhat anymore) - if you want to get RHL, you have to pay for it now. So it's not only for the media/documentation/support anymore. (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) 1) That is Red Hat's business model, but not always or exclusively. For example, Red Hat used to make a product named MetroX (I can't remember if it replaces XFree86 or a window manager), and buying a Red Hat CD gave you the right to install (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) I think that the analogy "computer program source" is to "compiled executable" as ".dat file" is to "rendered image" is, mostly, valid. In both cases, you take the source, run it through one of many programs (which may indeed give different (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) It wouldn't. But I would (could) prevent him (and everybody else) from distributing renderings that includes parts from the Parts Library, since these are derivative works of the parts in the Parts Library. (...) Agreed. But Larry's problem is (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | 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)
|
| |
| | Re: License Intent
|
|
(...) My understanding about that was that the charge was a media charge, not a charge for the library or work itself. In particular I thought a lot of the revenue that Red Hat receives is for support. Personally I could see some far fetched (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | 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)
|
| |
| | Re: License Intent
|
|
(...) <blink> How is the second item (a) a "protection" and (b) required by "the fundamental goals of Ldraw.org"? I would observe that Linux and the GNU Project seem to have done fine, despite frequent commercial redistribution for a charge (by Red (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) revise the (...) Yes, we're putting a lot of effort into getting this right. So, there shouldn't be any forseeable _major_ changes. To cite one example, IP law is continuously evolving; there may come a time when a change is required due to a (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: ldraw newbie
|
|
(...) It's a lot easier with a specialized minifig modeler program. There are several choices for the PC, but I don't know if MCB has one yet. Maybe you could try and convince Orion to work on his LDDP minifig modeler plugin to make it portable? I'm (...) (20 years ago, 4-Jun-04, to lugnet.cad)
|
| |
| | Re: ldraw newbie
|
|
(...) There are some shortcuts of fully assembled minifigs in the parts library, like 979.dat and 980.dat. Make a copy of one and do some experimenting on it. (20 years ago, 4-Jun-04, to lugnet.cad)
|
| |
| | Re: ldraw newbie
|
|
(...) I don't know why it looks like that, but using part 3209.dat works fine for me for a basic 2x3 slope brick. Do you know what number you were using? (...) I had a look at the file and I see the head is a bit mixed up. MBC has a few answers (...) (20 years ago, 4-Jun-04, to lugnet.cad)
|
| |
| | Re: ldraw newbie
|
|
Thanks, I was just moving bricks around the screen with the mouse; I hadn't reallized you could manually change the values. I tried putting together a minfig and this was much worse--I just couldn't get the arms to look right with the torso and then (...) (20 years ago, 4-Jun-04, to lugnet.cad)
|
| |
| | Re: June-Fourth Inccident Memorial
|
|
(...) To Dave: Oh thanks for giving such good comments! -David Chiu (20 years ago, 4-Jun-04, to lugnet.cad)
|
| |
| | Re: ldraw newbie [DAT]
|
|
(...) Hi Bruce! First, I have to admit I'm not familiar with Mac Brick CAD or even Mac. But I downloaded the buffalo ldr file and analyzed it in Windows Notepad. Step one: I changed the colour of the 3039.dat (Slope 45 2x2) to 47 (=Clear). I noticed (...) (20 years ago, 3-Jun-04, to lugnet.cad)
|
