 | | 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)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) Slightly better might be: 1x2 45 degree slope, end cap 2x2 45 degree slope, peak junction The way I have put my inventories in is to have the size be in a separate cell from the rest of the description, as a result, an alpha sort would put (...) (25 years ago, 7-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) I think that the word slope should be in there, along with the degrees of the slope. Those two slopes would then be "1x2 45 degree end cap slope" and "2x2 45 degree peak slope junction". Although, "half-pyramid" fits the "end cap" best, as (...) (25 years ago, 7-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
| |
| | Re: LDAO Suggestion Mark 3
|
|
I just keep a 0view.dat file in my /models directory ("0" so it's always at the top), and when I want to view .dats from the newsreader I launch the 0view.dat into LDAO's Editor, then with one cut-and-paste I can view a model. One more cut-and-paste (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev)
|
| |
| | Re: Parts Database (Was: Idea: ... Lego piece naming convention?) [DAT]
|
|
Ah, yet another promising database variant! This is great, and fast! I only see one problem with it is it only includes official LDraw elements. Isn't there any way we could make .DAT files for not yet rendered parts, too? Just for database (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) Why not add some new meta-commands? Either: 0 DEAFULTS COLOUR=15 ZOOM=150 (or 1.5) Or: 0 DEFAULT COLOUR 15 0 DEFAULT ZOOM 1.5 ... In fact, parts of the database could be hosted in the parts' .DAT files (to be continued in my posting subjected (...) (25 years ago, 7-Jul-99, to lugnet.general, lugnet.cad.dev)
|
| |
| | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) Would the plan be to include images for each part in each known colour? For the decorated parts, at least, I would prefer that the image uses a real life background colour rather than the default grey. As a reference for parts sales, etc it (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
