| | 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)
|