|
|
 | | 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 (...) (27 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 (...) (27 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 (...) (27 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?
|
| (...) For a lot of basic bricks, plates, tiles, etc, we seem to do OK. But other areas we seem to have trouble with the piece names. One area in particular that I've seen some problems are sloped brick peaks or apex bricks. Let's start there. Do we (...) (27 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?
|
| (...) My feeling is that it would be good to have a standard set of names for auctions and inventories. It would be nice if LDraw could use these names also, but sounds like there is good reason for it to use a different set of names. Two sets of (...) (27 years ago, 6-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
|
