 | | Re: Color Names
|
|
(...) This does apply to colors, albeit indirectly. A cross-reference would allow different sites/DBs to maintain different color names if they wished, and still translate between parts and colors. (...) Gaining cooperation for a cross-reference (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego)
|
| |
| | Re: Color Names
|
|
(...) I'd suggest that we keep the LEGO names in the database, as another naming scheme. That way, when we want to look up the LEGO name for a color, just look it up in the database. Better yet, when an AFOL calls LEGO and refers to OUR name for (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego)
|
| |
| | Re: Color Names
|
|
(...) Because unless TLC wholy converts over to using the same names that we do, it'd be nice to know what they're talking about when they start using a name that we don't. Also, it's nice to know what to ask for when you need to order a replacement (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego, FTX)
|
| |
| | Re: Color Names
|
|
(...) While this has absolutly nothing to do with color names, it is a good idea that Steve and I have been kicking around for a couple of years now. I know Richard from BrikTrak has already built some translation tables between Peerl/LDraw and BL. (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego)
|
| |
| | Re: Color Names
|
|
(...) I do not think anybody would need to "own" anything here (other than Lego). And I do not think any one site should be the leader with this. If the 3 sites chose to work something out then they should all have an equal say. As catalog admin on (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego, FTX)
|
| |
| | Re: Color Names
|
|
(...) Why do 'official' names matter, though? To me, the name useful to the community matters. -Tim (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego, FTX)
|
| |
| | Re: Color Names
|
|
(...) Because when a new color is introduced, it would help if people could infer the official name without having to ask for it. (...) What about previous colors? TLC might only have to be concerned about the current color pallete, but Bricklink (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego, FTX)
|
| |
| | Re: Color Names
|
|
(...) I think it's a good idea for LDraw.org to lead the way on this. Of course, as both of you mentioned, such project would include input from other groups. (...) I think instead of coming together and trying to hash out universal naming schemes (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego, FTX)
|
| |
| | Re: Color Names
|
|
(...) In the standard color wheel, pastels are achieved by adding white to a pure color, and earthtones are achieved by adding black, so I'm guessing the really dark colors are all termed Earth Something. The really confusing part is that I think (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego, FTX)
|
| |
| | Re: Color Names
|
|
(...) I know it's not, by definition, a LSC issue, but perhaps it should be. Much of the cross-site element "system" has been based on LDraw's part numbering and whatnot. If you look at Peeron, for instance, the parts are listed by their LDraw (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego, FTX)
|
| |
| | New Mini Moc: Proton
|
|
My New Mini Proton starship: (URL) Please visit my other galleries if you feel like. Operation Ice Cream (URL) Turtle (URL) Valkyrie (URL) VW-3000 Transporter (URL) TransCon Shuttle (URL) Shadow (URL) Owl (URL) H.A.P.C. (URL) C-47 Dropship (URL) (...) (20 years ago, 10-Jun-04, to lugnet.space, lugnet.cad, FTX)
|
| |
| | Re: Color Names
|
|
(...) The LSC could address this, but the LSC members aren't necessarily experts on the color palette. And it's an issue bigger than LDraw.org. So maybe a cross-organization group is called for? If we're going to talk about a 'system' for the color (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego, FTX)
|
| |
| | Color Names
|
|
All, I've seen many requests as of late to have LEGO release their color names for the specific brick colors. There has also been multiple requests for RGB/CMYK values and specific LEGO part numbers. Over the years I've addressed this question here (...) (20 years ago, 10-Jun-04, to lugnet.cad, lugnet.color, lugnet.lego, FTX)
|
| |
| | Re: License Intent
|
|
(...) Another question: if Joe submits a new file, and later on Jane fixes it, how much IP does Jane really have on the file? More concretely, we're fairly confident the Jessiman's will agree to license all of James' files to the (new) library. Many (...) (20 years ago, 10-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) Well, that's been our M.O. so far. So if we continue to distribute files under that umbrella, we won't be in any worse shape than we are now. (...) Yes. Agreed. However, we can (and probably should) start labeling everything that is covered (...) (20 years ago, 10-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
All what follows is my opinion only. (...) authors "give up copyright". Let's not confuse PD with right of redistribution. Let's not confuse giving up copyright with right of redistribution. What I am suggesting is that by posting a part to the (...) (20 years ago, 10-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) You are correct here, I should have used the term 'file' or 'work' instead of 'part'. From a copyright standpoint I mean 'work of an author'. (...) There are two ways to looks at this issue. 1) Get permission of all those involved and get them (...) (20 years ago, 10-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | 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)
|
| |
| | Re: License Intent
|
|
(...) Perhaps the book authors could share some insight on this, because there are many books out there containing renderings. What legal hoops did they jump through in order to publish? Don (20 years ago, 10-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
Steve said: (...) ... And Larry said: (...) Had to look up "tacitly": in a tacit manner; by unexpressed agreement; "they are tacitly expected to work 10 hours a day" And if I understand things correctly, you could argue that, but you'd be wrong :) (...) (20 years ago, 10-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) That depends on the license on the LDraw Parts Library and the LDraw file for the model/scene. (...) Exactly. (...) But since the _rendering_ of the DAT file _is_ a derivative work of the LDraw Parts Library, distributing the rendering may (...) (20 years ago, 10-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | 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)
|
| |
| | Re: META-command System For Creating Minifigs?
|
|
(...) There doesn't seem to be a standard, but I'd like one too. I'm hoping to make one by extending the LDAO MINIFIG META-commands, grabbing the part category lists from one of the extensible minifig part INI files available, and running it through (...) (20 years ago, 10-Jun-04, to lugnet.cad)
|
| |
| | Re: License Intent
|
|
(...) I agree. I just don't think we've come up with a better solution yet. Hopefully someone clever will spot the one we've missed so far! The problem with one library is that, to be fair, it sort of feels like we can't just wing it and say all the (...) (20 years ago, 10-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
What follows are my opinions, not vetted with the rest of the committee... (...) Yes. Personally I strongly agree that there ought to be baseline never to be changed conditions.. and that they ought to be named off. (note: that conflicts with using (...) (20 years ago, 10-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) I'm not philosophically opposed to an old/new library, but it would be awkward to administer. Especially if we suddenly started restricting ourselves from modifying the uncertified files. We'd start spending a lot of time explaining to people (...) (20 years ago, 10-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
In lugnet.cad.dev.org.ldraw, "Larry Pieniazek" <larry.(mylastname)@...areDOTcom> wrote: [snipped tons] (...) Sorry I'm coming late to this party... At some point in this thread, Larry stated something about 'decoupling' the two licenses. To some (...) (20 years ago, 10-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) How are parts individually copyrighted? Actually, what exactly is a 'part'? Is a shock absorber a single part, or an assembly of several parts? How about a minifig torso (as they exist in lego sets)? If you want to talk about have to copyright (...) (20 years ago, 10-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Straight moving with only one rotation sensor
|
|
Hello y'all- Does anyone out there know where I can get discontinued lego sets (mainly the autochassis set 8860&65) at reasonable rates here in Ontario? Thanks. (20 years ago, 10-Jun-04, to lugnet.cad.dat.ideas)
|
| |
| | Straight moving with only one rotation sensor [DAT]
|
|
Hi I saw in the LEGO Mindstorms Web Page that many people made their robots with 2 motors go straight using one rotation sensor on each wheel and stopping the correct motor until both sensors were equal. I got Ultimate Accessory Set as a present (...) (20 years ago, 10-Jun-04, to lugnet.cad.dat.ideas)
|
| |
| | Re: Problem with click hinge part(s)?
|
|
(...) my click hinges, and the lugs are ALL closer to the top of vertical end wall than the bottom. The position of the lug in your new version is definitely incorrect. Whether thats a problem with the primitive or the sub-part I don't know, but it (...) (20 years ago, 10-Jun-04, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Problem with click hinge part(s)?
|
|
(...) Actually its the other way about. 30387 is wrong. More accurately, the subpart s/30387s01.dat does not match the guidance notes in p/clh1 and p/clh4. 0 // Placement on side of bricks; rotate accordingly, 0 // place on side 10 Ldu below top (...) (20 years ago, 9-Jun-04, to lugnet.cad.dat.parts, FTX)
|
| |
| | META-command System For Creating Minifigs?
|
|
(...) If there is a universally working* META-command system for creating minifigs, be it LDAO's, LDDPMINIFIGGEN or any other, I'd like to push for it to be more or less an official standard. As I haven't been that engaged in this side of LCad, I am (...) (20 years ago, 9-Jun-04, to lugnet.cad)
|
| |
| | Re: ldraw newbie
|
|
(...) What do you think about the MLCAD.INI file format? It seems to contain the same sort of information as the minifig.ini file, but it's already documented, and so far it's been updated fairly promptly. It'd be really nice to standardize on one (...) (20 years ago, 9-Jun-04, to lugnet.cad)
|
| |
| | Re: BF 2004 LTC Container Car Swap Call for Participation
|
|
I am hoping that our club, ParLUGment, will be able to participate in the container swap. There are a couple of our members planning to attend, and I am trying to organize the creation of the containers, now that we've finally decided on a logo for (...) (20 years ago, 9-Jun-04, to lugnet.trains.org, lugnet.trains, lugnet.cad)
|
| |
| | Re: New Part: 30299.dat Rock Raiders Canopy base
|
|
(...) The link to the 30298.dat mockup has expired. Do you or anyone you know have a copy of it? (20 years ago, 9-Jun-04, to lugnet.cad.dat.parts)
|
| |
| | Re: Brick 2 x 2 with Wheels and Dually Wheels
|
|
(...) Well, I actually had to do this to modell the gap in the tube. Fortunately nothing broke. (On the other hand, I have plenty of these bricks, and I'll buy even more :-D ) (...) I have both versions. I have not changed the taps or clips in this (...) (20 years ago, 9-Jun-04, to lugnet.cad.ray, FTX)
|
| |
| | Re: License Intent
|
|
(...) I can appreciate the idea, but I doubt that you will be able to enforce that through a license for the parts library. Also, it is not always possible to implement a two-way converter between a pair of formats. Jacob (20 years ago, 9-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | 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)
|
| |
| | *** MLSave V1.10 ***
|
|
Hi to everybody! MLSave the first MLCad compatible screen saver for windows is now available in Version 1.10. New features are: - New option for randomly selecting a model from a directory - Perspective viewing of the model - New display action (...) (20 years ago, 8-Jun-04, to lugnet.cad, lugnet.cad.mlcad)
|
| |
| | Re: Non-commercial clause (was Re: License Intent )
|
|
(...) The GPL does not require re-submission to the original source. (...) You don't have to send the changes back to the maintainers, you only have to make the source of the changes freely available to everyone, you're even allowed to charge a (...) (20 years ago, 8-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Non-commercial clause (was Re: License Intent )
|
|
(...) Sorry - my mistake. (...) Ok, yes, that was my point - you can't keep the changes to yourself, you have to publish them, so that they could (in theory) be merged with the original library. (20 years ago, 8-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Brick 2 x 2 with Wheels and Dually Wheels
|
|
(...) My advise is: Don't try this at home! Those tap or clips broke very easily even when they were new, and I guess time hasn't made then less fragile... Then we had to fix them with a 3022 Brick 2x2 or a broken 650 Nylon Coupling (...) That was a (...) (20 years ago, 7-Jun-04, to lugnet.cad.ray, FTX)
|
| |
| | Re: Brick 2 x 2 with Wheels and Dually Wheels
|
|
Niels - Looks nice! On some of my older 2x2 wheel bricks there is a gap which allows the axle to be removed and/or snapped into the brick. On the newer bricks the metal axle cannot be removed (looks similar to your ldraw part). I'll see if I can (...) (20 years ago, 7-Jun-04, to lugnet.cad.ray, FTX)
|
| |
| | Part 2495, Minifig Hand Truck
|
|
Has anyone heard anything new about the minifig Hand Truck, part number 2495 (URL) ? Last thing I've noticed is from two years ago, someone said "nope, not yet". I was just seeing if anyone was working on it. It's not in the parts tracker, but that (...) (20 years ago, 7-Jun-04, to lugnet.cad.dat.parts)
|
| |
| | Re: Ebrace and Extend (was Re: Non-commercial clause)
|
|
(...) You are corrrect. Re-submission is not required. Library changes only need to be published. [snip] (...) Agreed. It is bunch of work for just about everybody involved. However, the result is typically better than if you go off on your own. (...) (20 years ago, 6-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: MakePart.c (Was: Baseplate generator program)
|
|
Hi, "Tore Eriksson" <tore.eriksson@mbox3...wipnet.se> schrieb im Newsbeitrag news:HywH7z.GLE@lugnet.com... (...) <SNIP> cool I'll give it a try! Thanks a lot, Michael (20 years ago, 6-Jun-04, to lugnet.cad.dev)
|
| |
| | Re: Ebrace and Extend (was Re: Non-commercial clause)
|
|
(...) Understood. (...) Agreed. (...) As long as people understand the trade-offs. Adding redistribution restriction clauses is tricky and hard to get right. Frequently people can work around them. (...) It is quite possible, although I doubt that (...) (20 years ago, 6-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: high res bushlocks? [DAT]
|
|
(...) You're probably right. I just remembered that the bushlocks are divided into 32 segments which is fairly colse to 48. Though the notches in bushloc3 would probably align better with the studs if they used the high res primitves at least in (...) (20 years ago, 6-Jun-04, to lugnet.cad.dat.parts.primitives)
|
| |
| | MakePart.c (Was: Baseplate generator program)
|
|
I knew I had it somewhere... If this code snippet can be of any use, anyone is free to use it. Notes: The main() is just an example on how to call the makepart() function. The groove option does not work. There really should be an outputfilename (...) (20 years ago, 6-Jun-04, to lugnet.cad.dev)
|
| |
| | Re: Brick 2 x 2 with Wheels and Dually Wheels
|
|
Well, I just gave it a try, and here are the results: (2 URLs) Since Peeron lists the dually (or double) tyre as partnumber 7b, I used 7b.dat for this tyre. I don't know the partnumber for the dually wheel, I used 20b.dat for now. These yet (...) (20 years ago, 6-Jun-04, to lugnet.cad.ray, FTX)
|
| |
| | Re: Problem with click hinge part(s)?
|
|
(...) without measuring, just by sight, I'd say the 1x2 is the incorrect one, it's lugs should be moved up to match the 1x4 ROSCO (20 years ago, 6-Jun-04, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Problem with click hinge part(s)?
|
|
(...) Joel Thanks for bringing this to our attention. I'll do what I can to correct the official part library in the next parts update. Chris Dee (20 years ago, 6-Jun-04, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Baseplate generator program
|
|
Lester, I would like to include that into MLCad. Adding as a meta command for MLCad I could support this. All I would need is some sort of library I can use. Best way would be a dll, which generates that - or if you do not mind already the source (...) (20 years ago, 6-Jun-04, to lugnet.cad.dev)
|
| |
| | Re: Ebrace and Extend (was Re: Non-commercial clause)
|
|
(...) It is my understanding of the GPL that no such re-submission is required. As long as you agree to the GPL terms and give appropriate credit to the original author, you can publish your mods as a separate work (or upgrade) under the GPL. (...) (20 years ago, 5-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Ebrace and Extend (was Re: Non-commercial clause)
|
|
(...) I agree that GPL might not be the right license to use here - I was just using it as an example of how the "extension" problem might be dealt with, as far as the license goes. Of course that we would always want the LDraw format to be the most (...) (20 years ago, 5-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Ebrace and Extend (was Re: Non-commercial clause)
|
|
(...) (For those of you who do not know, GPL=Gnu Public License.) GPL is one strategy. I prefer an innovate over litigate strategy. The GPL is complex and in certain critical areas extremely vague. The GPL attempts to mandate innovation by requiring (...) (20 years ago, 5-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Non-commercial clause (was Re: License Intent )
|
|
(...) Wouldn't this problem be solved by the GPL approach, where any modifications made have to be re-submitted to the original library? This way, yes, you can make your cool changes, and sell them, but you have to send the patches back to the (...) (20 years ago, 5-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Non-commercial clause (was Re: License Intent )
|
|
(...) [snip] (...) It is very hard to define what commerical vs. non-commercial use is as the examples above demonstrate. One of the best ways to ensure that part authors do not feel "ripped off" is to ensure that the library is alwasys freely (...) (20 years ago, 5-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | part 47405
|
|
can anyone create part 47405? (maersk ship boat base part) i think i figured out a way to enlarge and create a somewhat minifig scale maersk ship. (similar to scale from the launch and load seaport) (20 years ago, 5-Jun-04, to lugnet.cad)
|
| |
| | Re: License Intent
|
|
I have to agree (and I know as a non-part author myself other than pathetic attempts which never saw the light of day by point will be held in less regard than those of actual offical part authors') that all parts should be open source. Not that (...) (20 years ago, 5-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Unknown part: Brick 2 x 4 with hole
|
|
Among a lot of 2nd hand lego from the seventies (ca 1971 - 1977, no older bricks) I found a red 2x4 brick with a small hole in the top. The hole looks perfect, so I don't think someone has drilled it in the brick. I could not find any reference (...) (20 years ago, 5-Jun-04, to lugnet.general, lugnet.cad)
|
| |
| | Re: high res bushlocks?
|
|
(...) I think they are fine the way they are. The basic reason is size. The bushlocks are 20 LDU in diameter. 48-segment primitives are not needed until you get to 80 LDU diameter curves. If you need to put 48-segment primitives with a bushlock, (...) (20 years ago, 5-Jun-04, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Looking for Roborider parts
|
|
(...) I believe both of those parts are on the Parts Tracker. Search through the list at (URL) (20 years ago, 5-Jun-04, to lugnet.cad.dat.parts)
|
| |
| | Re: ldraw newbie [DAT]
|
|
(...) Do you mean LDraw meta-commands? Or some command system called META? Anyway, you could look at LDAO's set of meta-commands for modelling minifigs. At least as a starting point. It's pretty straight-forward. LDAO's minifig modeller generates (...) (20 years ago, 5-Jun-04, to lugnet.cad)
|
| |
| | Re: ldraw newbie
|
|
(...) It's simple. I'll write at post it this weekend. (...) For cross platform compatibiliy, since I can't write a GUI, I have to parse META commands. Here's an example: 0 LDDPMINIFIGGEN HEAD 3626B 14 45 This would output a minifig with the (...) (20 years ago, 5-Jun-04, to lugnet.cad)
|
| |
| | Re: ldraw newbie
|
|
(...) Yeah, but there are cross platform toolkits for that sort of thing. I was thinking of using your minifig.ini file. I like the extensibility that it offers. I think I could whip up something portable pretty quick if I saw how you parse the ini (...) (20 years ago, 5-Jun-04, to lugnet.cad)
|
| |
| | Re: ldraw newbie
|
|
(...) The vast majority of my work is in Delphi (with a small smattering of C and VB for good measure) As far a portabiliy is concerned, I'm not sure if I can. The way windows are created across platform is fundimentally different. I would have to (...) (20 years ago, 4-Jun-04, to lugnet.cad)
|
| |
| | Re: ldraw newbie
|
|
(...) LOL. Yeah Orion, how about it? :-) What is it written in now? James (20 years ago, 4-Jun-04, to lugnet.cad)
|
| |
| | Re: License Intent
|
|
(...) As a parts author who is likely to go inactive to the future (parts authoring, I've noticed, comes in spurts), I'd like to see the following: License dictates that any future changes need author approval. A majority of authors approving is (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) So exactly how would someone release a rendering in complience with open source ? The DAT file associated with the render is not subject to the open source rules (since it is not a derivative work but merely references the library as a tool) (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) That would be great - but are you going to ask them also to distribute the latest copy of the library from their site? Or on any of the media they distribute? Is that something we want? The answer might be yes, but I don't think it should be. (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) (personal thoughts) I think your suggestion could work. I'm very wary of requiring absolute explicit permission for any future changes, though I do want to ensure the authors' wishes are considered in potential future changes. The reason is, (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) <snip> (...) I'm positive you are much more aware of the names problem than myself and 99% of the total community...... If the names were in numeric form this would not be an issue. As we all know the molds have numbers, sets have numbers.... (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) Is a non commercial clause part of the SteerCo's intent? It wasn't mentioned in the initial post or in Larry's update. Could you clarify for me? Discounting the use of rendered parts in commercial products, eg. Larry selling ldraw rendered (...) (20 years ago, 4-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | 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)
|
| |
| | ldraw newbie
|
|
Hi all, I finally gave Ldraw a try, primarily to help me make instructions (though in the future I'll probably use this in the design stage for larger models). Right now I am just using the simplest features on Mac Brick CAD v 2.3b1, on a Mac using (...) (20 years ago, 3-Jun-04, to lugnet.cad)
|
| |
| | Re: New Part: 30176.dat - Plant Brick 1 x 1 Round with 3 Bamboo Leaves
|
|
(...) Wow! You are my hero :-) Now I can finish modelling and rendering my latest creation: House on the Hill. Pictures soon. Thanks Tore! Jaco (20 years ago, 3-Jun-04, to lugnet.cad.dat.parts)
|
| |
| | Re: Plant Brick 1 x 1 Round with 3 Bamboo Leaves
|
|
(...) You are too kind :-) (20 years ago, 3-Jun-04, to lugnet.cad.dat.parts)
|
| |
| | Re: Question about creating Cone 4 x 4 x 3 for LDraw
|
|
(...) Okay, thanx for the answer. The part is now on the Parts Tracker as x272.dat Niels (20 years ago, 3-Jun-04, to lugnet.cad.dat.parts)
|
| |
| | Re: June-Fourth Inccident Memorial
|
|
(...) Never mind--I figured it out (I should have realized it in the first place). (URL) *really* like these, and there's nothing wrong with using a political subject in your artwork! Thank you for sharing your commemoration of this event! Dave! (20 years ago, 3-Jun-04, to lugnet.cad)
|
