 | | Re: [LSC] Colour Definition meta-statement
|
|
(...) I don't think so. What if CODE is part of the color name? I can't think of a quick example for that, but other key words are easy. AlphaTeamRed, BlueChrome... I'll support color names with no space characters, and I'll consider supporting (...) (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Bylaws Draft
|
|
(...) Well put! (...) Typically if there is no explicit bar, the interpretation is that multiple terms are OK. That could be added if it's really unclear. As to the term length, ILTCO went with 2 year terms for the executive committee for reasons (...) (21 years ago, 23-Jan-04, to lugnet.cad.dev.org.ldraw, FTX)
|
| |
| | Re: LDraw.org Bylaws Draft
|
|
I think this is a good thing and would really turn LDraw into a machine that gets more things done. I've been heavily involved with Mac OS X Labs Org ((URL) for the last year. The steering committee for that group has had weekly conference calls and (...) (21 years ago, 23-Jan-04, to lugnet.cad.dev.org.ldraw, FTX)
|
| |
| | Re: LDraw.org Bylaws Draft
|
|
I put my reply at the top on purpose... I think we're all agreed on the intent but I'm not sure we have the wording nailed. "professional" is a harder word to define and agree on the definition of, than "student" or "part-time"... So while I'm OK (...) (21 years ago, 23-Jan-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) Disregard the NAME suggestion. I'm brain dead today. -Orion (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) How about NAME? (...) I don't see a problem with this. Steve or Jacob? -Orion (21 years ago, 23-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I won't make any guarantees, but there's a reasonably high probability that I won't even try to support the above, even if it's what the spec says in the end. It's too much of a pain. Additionally, it disallows further expansion of the colour (...) (21 years ago, 22-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) HTML uses # (...) The name should be the characters after the !COLOR keyword and before the next keyword. The only contraint I can think of is that is not be one of the other keywords. (...) ALPHA should apply to the VALUE color and the color (...) (21 years ago, 22-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) I prefer the currently used 0x prefix, but I guess if you picked # to match other file formats in use by ldraw users then I can live with it. I forget, does POV or HTML use # for the hex prefix? (...) No spaces in the name? Alpha-numeric only? (...) (21 years ago, 22-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Bylaws Draft
|
|
(...) Your reasoning is sound and your edits seem reasonable to me at first read. In the interest of full disclosure, I am a part-time retail employee of the LEGO Company, and a full-time student. I'm not involved in any strategy decisions as a part (...) (21 years ago, 22-Jan-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: LDraw.org Bylaws Draft
|
|
(...) The text generally looks good, but ... (...) [...] (...) This distinguishing between part-time and full-time employees seems very artificial to me in this context. I think that all the organisations that I have been employed by here in Europe (...) (21 years ago, 22-Jan-04, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: 81 million points
|
|
(...) I forgot to mention. I didn't try fly-through mode, but wouldn't expect it to be very usable at 1 frame per second. --Travis (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: 81 million points
|
|
(...) My system is a 2.4GHz P4 with 1GB RAM. However, according to the Windows XP task manager, LDView was only using about 125 megs when the model was loaded with normal-res studs. (This compares very favorable with the current LDView release that (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: 81 million points
|
|
(...) Wow. That must be amazing in fly-thru mode. I'm also curious. What sort of CPU and how much memory do you have, and how much of that was in use by the LDVIEW? (...) I bet you have to get all your display list(s) and vertex arrays into the (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Bram's LDraw and LEdit Tutorial
|
|
(...) I have a copy. Let me know if you still need it and I can email it to you. I still point to the LEDIT portion of this tutorial in the ldglite instructions so I'd like to see this back on the internet somewhere as soon as possible. Don (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Bram's LDraw and LEdit Tutorial
|
|
(...) Name: ldrawtutorial.zip Size: ~410K -Orion (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) Color codes will be defined in decimal notation and the 24-bit RGB will be in Hex. -Orion (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
(...) RGB is actually 3 numbers - I'd suggest something like RGB(r,g,b) where r g & b can be decimal or hex as per other numbers. ROSCO (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Bram's LDraw and LEdit Tutorial
|
|
(...) What would the name of the file be and how big is it approx.? Then I can browse through my 6 year old collection of "Download CD's..." :-) Jaco (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | 81 million points
|
|
I normally don't make posts like this, but I thought the numbers involved deserved a post. Just out of curiosity, I stuck a counter in my development LDView code to count the number of points being drawn. I loaded up the copy I have of town.dat (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: [LSC] Colour Definition meta-statement
|
|
I'll bite. (Note that none of my comments are meant as criticism.) In lugnet.cad.dev, Steve Bliss wrote: <SNIP> (...) I personally think the # for hex numbers is a mildly bad idea. The currently accepted way to specify hexidecimal values is to (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | [LSC] Colour Definition meta-statement
|
|
Here's the initial write up for a color definition meta-statement, to be used in ldconfig.ldr and in any model file. The LSC has a couple of outstanding issues with this spec, let's discuss those in follow-up messages. Please respond with any (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Matrix mirroring question
|
|
This question is mostly directed a developers that have had to deal with mirroring while processing LDraw files, but I welcome comments from anyone. It seems to me that any model specified with a mirror matrix will be mirrored relative to its parent (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Save that code! Once an LDraw/POV-Ray library is a going thing (and it looks like that won't take so long), those parts can be submitted there. Steve (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) True, but the 'embedded code' is still code we are effectively certifying as being good, whether it works strictly within LDraw, or in other GDL/SDL's. (...) Sorry, we never got around to making the list public. I'll work on that. Steve (21 years ago, 21-Jan-04, to lugnet.cad.dev)
|
| |
| | Bram's LDraw and LEdit Tutorial
|
|
Attention all, Thinkquest, the site that hosted Bram's LDraw & LEdit Tutorial, recently deleted this tutorial from their archive. Neither Tim nor I had a hard copy of the webpages. While I've contacted Bram asking him if he still has a copy, I'd (...) (21 years ago, 21-Jan-04, to lugnet.cad, lugnet.cad.dev)
|
| |
| | Re: Adding part updates (and clone parts)
|
|
(...) snip (...) Hey Don, When I click a [DAT] link the windowbar of the ldglite window says "/Users/cjmasi/Deskt.../mini.dat" which is where the dat file is put before is it handed off to ldglite. If I do a "control click send to ldglite" the (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev.mac)
|
| |
| | Re: Adding part updates (and clone parts)
|
|
(...) I wouldn't bother too much about that issue. With a fair computer (P120 and above) and not any extremely huge models, the difference in rendering time is hardly noticable. Just add <zero>* BFC NOCERTIFY and you have a really quick and easy fix (...) (21 years ago, 21-Jan-04, to lugnet.cad.dev.mac, lugnet.off-topic.clone-brands)
|
| |
| | Re: Adding part updates (and clone parts)
|
|
(...) Glad you asked, because it gives me another good excuse to get off my duff and finish what I started. My collaborator in setting up a clone.dat website has been very patient with my procrastination, and he's put together an attractive site (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev.mac, lugnet.off-topic.clone-brands)
|
| |
| | Re: Adding part updates (and clone parts)
|
|
(...) I believe one of you Mac guys may have actually inquired about the clone part files at one point. So clone part makers, what's the current status? I have a copy of clone001.zip. Should I make that available from the Mac ldglite startup page, (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev.mac, lugnet.off-topic.clone-brands)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
In lugnet.cad.dev, Kevin L. Clague wrote: [much snippage] (...) The above example parallel directory structure is just an example. I see that there are many possible alternate solutions... POV directory as sigbling of LDRAW subdirectory, where the (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) One thing the project clearly needs right now is a small homepage to tell what it's all about, and outline what people can do to help. That might help pull in more active participants than a lone CVS archive. I've seen your pages, Larry. I bet (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
In lugnet.cad.dev, Larry Pieniazek wrote: <much snippage> (...) As Orion described, we'd rather put the ability of using POV or whatever other renderer you choose outside the LDraw file format, and outside the LDraw format parts library. If we (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) The relatively easy solution on how to make the wrench tool and, even more obvious, the (unofficial) patterned maxifig heads - that solution has become undone. (...) The only thing that ever has frustrated me about LGEO is that I never ever (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) What's entailed? Do you want participants who can test but not do much else? (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Actually, the only Official Library parts that have embedded P-R SDL are some of Paul Easter torus primitives. Since nothing was ever done in the first place, nothing is being undone now. If you're like me and frustrated that LGEO is (...) (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Only until 3rd party libraries (like LGEO) become available. ROSCO (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Too sad. If I got that complicated language correcly, this means that the problem presented at (URL) and was solved by embedded POV-code has now regressed to be un-solved again. /Tore (21 years ago, 20-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) Yes, and if you want to join the project team let me know (this goes for anyone else as well). (...) -Orion (21 years ago, 19-Jan-04, to lugnet.cad.dev)
|
| |
| | Re: Change to existing policy on embedding POV-Ray code in Official Files
|
|
(...) OK, but whether or not the P-R SDL code was out of whack would not affect the usability of parts as parts within LDraw format programs themselves, right? (0)Only affect the accuracy or completeness or error state of transformation (by tools (...) (21 years ago, 19-Jan-04, to lugnet.cad.dev)
|
