 | | Re: New LDraw based editor... GLIDE. Click authors required.
|
|
I guess I'm thinking about this differently. It's not that the individual studs on the brick don't allow other mating angles. (IE you can place a 1 x 6 technic plate with rounded ends on any single stud at some funcky angles) It's the combination of (...) (20 years ago, 23-Jun-04, to lugnet.cad, lugnet.cad.dev.lcd, lugnet.cad.dat.parts)
|
| |
| | Re: New LDraw based editor... GLIDE. Click authors required.
|
|
(...) I really like the way the .dat format reuses geometry e.g. stud.dat. I think the clicking format should be able to do the same thing. I imagine that would be quite a bit more difficult to reuse if the clicking info was in the dat files. (...) (...) (20 years ago, 23-Jun-04, to lugnet.cad, lugnet.cad.dev.lcd, lugnet.cad.dat.parts)
|
| |
| | Re: New LDraw based editor... GLIDE. Click authors required.
|
|
(...) I do indeed think it would be undesirable. As we all know Stud.dat gets used every ware. There are a fair few instances were the clicking behaviours of two bricks would be different even though they are both referencing the same stud.dat file (...) (20 years ago, 23-Jun-04, to lugnet.cad, lugnet.cad.dev.lcd, lugnet.cad.dat.parts)
|
| |
| | Re: New LDraw based editor... GLIDE. Click authors required.
|
|
(...) I agree, but in the short term, I think seperate files may be simpler. (...) I thought so too, but the format document (way at the bottom) implies that this might be undesirable. I'm not sure I understand why, though : ( (20 years ago, 22-Jun-04, to lugnet.cad, lugnet.cad.dev.lcd, lugnet.cad.dat.parts)
|
| |
| | Re: LDBoxer - Next Step and My Datsville Plans
|
|
(...) (snip) (...) I *am* working on it, though slowly :-( The idea is that you can specify any number of part directories, e.g.: <MODELDIR> <LDRAWDIR>\P <LDRAWDIR>\Boxer <LDRAWDIR>\Boxer\B <LDRAWDIR>\Boxer\B\A <LDRAWDIR>\Boxer\BB <LDRAWDIR>\PARTS (...) (20 years ago, 22-Jun-04, to lugnet.cad.dev)
|
| |
| | Re: New LDraw based editor... GLIDE. Click authors required.
|
|
(...) There's a difference between supporting POV inline (which is not controlled in the community) and supporting LCD info (which could be integrated into the DAT format). I'd like to see programs support both options - both as an external .lcd (...) (20 years ago, 22-Jun-04, to lugnet.cad, lugnet.cad.dev.lcd, lugnet.cad.dat.parts)
|
| |
| | Re: New LDraw based editor... GLIDE. Click authors required.
|
|
The it would be slick to have the LCD info in the dat file, but it might complicate issues being dicussed by the Ldraw committee : ( It seems that pov style includes aren't allowd in official files either so maybe keeping it seperate for a while (...) (20 years ago, 22-Jun-04, to lugnet.cad, lugnet.cad.dev.lcd, lugnet.cad.dat.parts)
|
| |
| | Re: New LDraw based editor... GLIDE. Click authors required.
|
|
(...) inline in a valid DAT file? Perhaps make all the lines start with a "0 LCD" before anything else? Then, when reading a DAT file, a program can recognize and parse LCD info, in addition to looking for the .lcd file. Does that make sense? Do you (...) (20 years ago, 22-Jun-04, to lugnet.cad, lugnet.cad.dev.lcd, lugnet.cad.dat.parts)
|
| |
| | Re: New LDraw based editor... GLIDE. Click authors required.
|
|
Hi Glide has been on hold now for about a month but its back in development. You can look forward to clicking bricks in about two to three weeks. Once I have the system implemented is there anyone out there who would be prepared to start writing (...) (20 years ago, 22-Jun-04, to lugnet.cad, lugnet.cad.dev.lcd, lugnet.cad.dat.parts)
|
| |
| | Re: Mac Brick CAD 2.3b2
|
|
(...) Thanks for getting this out for us, Andrew! Even though the URL above doesn't work I was able to grab it and am now happily using it! (It should read mbc.html at the end I believe...) Greetz, Anton (20 years ago, 21-Jun-04, to lugnet.cad.dev.mac)
|
| |
| | Re: LDBoxer - Next Step and My Datsville Plans
|
|
(...) Well, I tried to pull you into the discussion at least twice, by mentioning your boxer subdirectories, but no luck. (URL) think some sort of consensus *was* reached and Lars was working on some reference code to handle it. But I have to admit, (...) (20 years ago, 21-Jun-04, to lugnet.cad.dev)
|
| |
| | 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)
|
| |
| | Re: LDBoxer - Next Step and My Datsville Plans
|
|
(...) That's not a bad idea, but the advantage of messing up the PARTS\ folder is that no extra adjustment or setup will be required. (...) "121 Messages in This Thread" - It's very hard for anyone who did not participate in the discussion to find (...) (20 years ago, 21-Jun-04, to lugnet.cad.dev)
|
| |
| | Re: LDBoxer - Next Step and My Datsville Plans
|
|
In lugnet.cad.dev, Tore Eriksson wrote: [Lot of snippage] (...) hi tore, with the release of MLCad 3.10 there are now at least two progs who support custom folders. instead of messing up my PARTS\ and P\ folder I wish I could define something like (...) (20 years ago, 21-Jun-04, to lugnet.cad.dev)
|
| |
| | Re: Primitive Generator program update
|
|
(...) hi paul, could you on the fly have also a look at your calculator? I would appriciate very much if you could add the Ctrl+C, Ctrl+V and Ctrl+X shortkeys and fix the behavior of the fields when deleting all numbers, esp. with the backspace key. (...) (20 years ago, 21-Jun-04, to lugnet.cad.dev)
|
| |
| | Re: Primitive Generator program update
|
|
(...) Ok, I will look into that. Thanks, Paul (20 years ago, 20-Jun-04, to lugnet.cad.dev)
|
| |
| | Re: Primitive Generator program update
|
|
(...) I can do that. Now why didn't I know that CCW was the standard winding? Maybe the 2x4 didn't hit hard enough? ;) Paul (20 years ago, 20-Jun-04, to lugnet.cad.dev)
|
| |
| | Mac Brick CAD 2.3b2
|
|
Just a quick note, I've placed MBC 2.3b2 on my .mac site (URL) is only a minor fix update, * Improvements to the render engine * Bug fix for the display of .mpd files * The Imperial Star Destroyer will render about 2 seconds quicker on my system (...) (20 years ago, 19-Jun-04, to lugnet.cad.dev.mac)
|
| |
| | Re: Primitive Generator program update
|
|
(...) One bug I've found so far: When I enter a value in the size (radius) box, the filename of the generated part does not use this value. When I use the up/down buttons, the filename is correct. For a large radius it is more convenient to enter (...) (20 years ago, 17-Jun-04, to lugnet.cad.dev)
|
| |
| | Re: Primitive Generator program update
|
|
(...) Can you set the BFC so the default winding is CCW? That is the standard winding for primitives in the part library. Steve (20 years ago, 17-Jun-04, to lugnet.cad.dev)
|
| |
| | Primitive Generator program update
|
|
Does anyone have any errors or things that need fixing for the next release of the primitive generator. So far the only thing I have planned to do is making the remove leading zeros (built in function) become an option in the options menu. This will (...) (20 years ago, 17-Jun-04, to lugnet.cad.dev)
|
| |
| | 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)
|
| |
| | Re: Questions On ldconfig.ldr (Was: colours.txt -> LDraw-org Official Part Updates!)
|
|
(...) Yes, that's exactly what I'm suggesting. And the database should be text-based, space-delimited, available offline to all softwares that may need the info - and udpated regulary. In other words: in the new, improved ldconfig.ldr! :) /Tore (20 years ago, 16-Jun-04, to lugnet.cad.dev)
|
| |
| | 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)
|
| |
| | 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)
|
| |
| | Re: License Intent
|
|
(...) Actually I beliee that this is the exact case where the LGPL differes from the GPL. Since the Parts 'library' will only be referecned as a library, I think that (if the LGPL were used on it,) it's license wouldn't pollute the license of the (...) (20 years ago, 11-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: License Intent
|
|
(...) I doubt it. Going by what I've seen in the Open source programming environment, the file's original author is considered the copyright owner, even after someonelse makes a bug fix or some other tweak. If the change is big enough, (whole new (...) (20 years ago, 11-Jun-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Leaving Brand Retail
|
|
As quite a few of you know, I've been working part time at the Woodfield LEGO store since it opened last October. During my time there, I had the joy of seeing many familiar LUGNET faces pop by, and even was able to meet a few new people as well. I (...) (20 years ago, 11-Jun-04, to lugnet.people, lugnet.cad.dev.org.ldraw)
|
| |
| | 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)
|
