|
|
 | | 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)
| | | | | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
| Simon Robinson wrote in message ... (...) and (...) Hey, those aren't "hollow space wheels", they're "podracer jet engines"... Frank (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'd agree. In principle, where bricks do have obvious uses you'd need to keep that use in the name for simplicity. After all, I'm sure it wouldn't be too hard to find some exotic uses for wheels, but is anyone seriously going to suggest that (...) (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?
|
| Todd Lehman wrote in message ... (...) I haven't inventoried my copies yet, and still have them in the bags. Both of mine, bought from two different stores, had the same set of bags. The bags in the inner box: 1 bag with long grey beams 1 bag with (...) (25 years ago, 7-Jul-99, to lugnet.admin.database)
| | | | | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
| John Matthews wrote in message ... (...) different (...) I think parts descriptions have to assume a "top/up" of a part, otherwise, we'll have really long names" "5x5x2 rectangular piece with one stud centered on one 5x5 face with hollow on (...) (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?
|
| (...) [followups to lugnet.admin.database] Heather, I happen to have that one inventoried... I can't make any promises that this is 100% correct, but I'm pretty comfortable with it, actually having double-checked it a couple of times. Sorry it (...) (25 years ago, 7-Jul-99, to lugnet.db.inv, lugnet.admin.database)
| | | | | What's in 8277?
|
| Hi folks, I have an opened copy of 8277 (the biiig Technic robot) that I'd like to trade or sell, but I have no idea whether it's complete. The present pieces are still in bags and a box, but whether there are any missing inner containers is (...) (25 years ago, 7-Jul-99, to lugnet.admin.database)
| | | | | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
| (...) Words can't be copyrighted (well, maybe supercalifrigilistic...alidocious can be :-) but trademark searches are free at the USPTO (but they're delayed by 2 months so that they can charge fees for up-to-date searches). USPTO search of their (...) (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?
|
| (...) Just my .02 Sterling: This word might already be copyrighted and / or trademarked. How cheap is a copyright search? Also -- I kinda prefer the one without the "k". I guess it boosts our class if we're building with fancy Lego "bric"s rather (...) (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?
|
| (...) Darnit, I can't spell today. :-) That should be "Bricktionary." --Todd (25 years ago, 6-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?
|
| (...) As they say in Canada, Minnesota, and Maine, "O-ya, it's been parta da plan since day one." :-) Lots of little prototypes and mock-ups and discussions here and there. Sill a ways off from fruition, though. But I think it's one of the very most (...) (25 years ago, 6-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?
|
| (...) Sybrand, Since you're looking at an incredibly huge undertaking, be sure to seek out and make the most of every last bit of info you can find on the net about anything related to this. (But don't give up! :-) Here are some related things which (...) (25 years ago, 6-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 it would be unwise to use words such as vertical clip or gable in part nomenclatures. The gable end piece was designed to be used to complete the gable of a roof, yet it might be used for an entirely different purpose. A 1 x 1 with (...) (25 years ago, 6-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?
|
| (...) To start with the second point you mention: I don't think anyone should be obliged to used the `standard' nomenclature. As you say, for different applications the best name to use can vary for a piece. Even, if one wants to call a 1x1 brick a (...) (25 years ago, 6-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?
|
| (...) areas (...) I've (...) Do (...) which I (...) what (...) among (...) lot of (...) Another one which would be good to have a concise name for are the various "connector" pieces, especially for the 1x1 plate with side clip. I could see the one (...) (25 years ago, 6-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
| | | | | Re: Updates on train items
|
| (...) Here's a couple items from the US Summer 1999 S@H catalog (prices are S@H catalog price): 4541 Road N'Rail Service Truck (slightly different name) $14.50 4556 Train Station (per catalog is 233 pieces, I check this at home in the next couple (...) (25 years ago, 6-Jul-99, to lugnet.admin.database, lugnet.trains)
|
|
