 | | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) They weren't. (...) They were discussed openly -- several times. Probably the reason they were easy to miss was because they were discussed in RTL, where things get lost easily and it's harder to go dig stuff up later. --Todd (25 years ago, 8-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?
|
|
In lugnet.admin.database, Todd Lehman writes: <snip> (...) hey, how come these thing were keep in the dark? thing like that should have been open to public long ago. Martin (25 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
| |
| | Re: What's in 8277?
|
|
Well, look at that, my set is complete! Thanks very much, you've saved me a character building experience... Want a third set at a discount? Heather (...) (25 years ago, 8-Jul-99, to lugnet.admin.database)
|
| |
| | Re: Parts naming conventions
|
|
(...) Exactly. If everyone assumes a set starting orientation, such as the word "lego' on the studs is right side up readable from left to right then it would be trivial top decide upon a convention for describing a particular side or top/bottom. (...) (25 years ago, 8-Jul-99, to lugnet.admin.database)
|
| |
| | Re: Parts naming conventions
|
|
Jim Hughes wrote: <snip> (...) Right. And you could denote whether a thingabob was vertical or horizontal with a variant on the cis/trans nomenclature as well, instead of using vertical. if we agreed that "cis" (or whatever we picked) meant an (...) (25 years ago, 8-Jul-99, to lugnet.admin.database)
|
| |
| | Parts naming conventions
|
|
I didn't know exactly where this fit into the thread so I just started a new one. Read with interest the discussion of part naming conventions as this is something I have been (trying) to deal with for several years as part of my element registry. (...) (25 years ago, 7-Jul-99, to lugnet.admin.database)
|
| |
| | 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: What's in 8277?
|
|
Hi Todd, Oh, super, thanks very much. There's a picture on the inner box of the completed module that's made from the parts inside, so I can sorta tell what's there. I'm sure I'll be able to tell if there are great gaps (ie. a whole bag) even if (...) (25 years ago, 7-Jul-99, to lugnet.admin.database)
|
| |
| | Re: A couple of data points
|
|
Simple Solution (lot's of fields): piece_count_box=123 piece_count_cat=124 piece_count_hand=122 piece_count_instruct...s_main=104 The last one is interesting since you could do piece inventories from instructions alone. KL (...) (25 years ago, 7-Jul-99, to lugnet.admin.database)
|
