 | | [ldraw.org] Thank You
|
|
I would like to thank the following people on their contributions to the ldraw.org project: First and foremost, the biggest thanks goes to Jacob Sparre Andersen. Jacob donated the server space for ldraw.org and has played a HUGE role behind the (...) (25 years ago, 7-Jul-99, to lugnet.announce, lugnet.cad.dev, lugnet.admin.general, lugnet.cad.dev.org.ldraw, lugnet.general)
|
| |
| | [ldraw.org] Site Release!
|
|
I am pleased to announce the ldraw.org website is now online and open to the public! Please visit and enjoy. :) (URL) no means is the site or the project complete. I have done all I can to present the site neat and tidy with placeholders where (...) (25 years ago, 7-Jul-99, to lugnet.announce, lugnet.cad.dev, lugnet.admin.general, lugnet.cad.dev.org.ldraw, lugnet.general)
|
| |
| | Re: LDAO Suggestion Mark 3
|
|
Interesting idea. I will add to my ToDo file. But I think I'll mull it over for awhile before acting on it. I also like John's suggestion. Steve (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) I hope not. That would limit the site to serving up images in predefined colors. Two bad results: the list of predefined colors could become outdated, and some people might have a reason for making up their own color values for parts. I'd (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | Re: Parts Database (Was: Idea: ... Lego piece naming convention?)
|
|
(...) How about a 0 IMAGE meta-command, for those parts which are not-yet coded? That way, we could supply a URL for all parts, and the image could come from any source. Of course, it might make more sense to have that particular item as a column in (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) OK. I agree with you. The idea behind my site was to help people who are trying to locate hard-to-describe pieces, and need to visually browse through the catalog. (...) Again, I agree. I was just brainstorming ideas on how to reduce the (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | Re: Parts Database (Was: Idea: ... Lego piece naming convention?)
|
|
(...) Creating shell .DAT files is a simple way to record information for parts which haven't been created for LDraw. I wouldn't include these shell files in the L-CAD parts updates, but they would be useful for building a parts-base. (...) That (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev)
|
| |
| | Re: Parts Database (Was: Idea: ... Lego piece naming convention?)
|
|
(...) Definitely don't forget LDList! It's a great tool for finding parts. :) Steve (25 years ago, 7-Jul-99, to lugnet.general, lugnet.cad.dev)
|
| |
| | Re: can parts authors try to finish what they have started?
|
|
(...) So why should it be on the Parts Tracker? I made a *mockup* file. That's different from working on a file worth including in a parts update. (Those studs inside the inverted slope are killers) Steve (25 years ago, 7-Jul-99, to lugnet.cad.dev)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) One neat thing that can be done if the pictures are served up by a cgi script is to store only a single image, but go in and modify the color before shipping it out. Of course you would need a standard set of color names, and a syntax for (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
