|
|
 | | if i modeled the monorail points would i have to model the inside?
|
| if i modeled the monorail points would i have to model the inside? i do not particularly want to as it would mean more work for me... (25 years ago, 9-Jul-99, to lugnet.cad.dev)
| | | | | can i use a povray library as a reference?
|
| can i use a povray library as a reference? i have one that has a part i want (the lower_trainnose to be exact) amd i planned to use the povray object as a reference to model the part in ldraw. (25 years ago, 9-Jul-99, to lugnet.cad.dev)
| | | | | (canceled)
|
| | | | | | Re: Newsgroup for this (was Re: The Bricktionary project)
|
| (...) Right. Identification and reference and browsing and all that. Massively cross-referenced within itself and to/from set inventories, MOC's, and the marketplace. So it's really a sub-database of the larger database. The "Brictionary" part is (...) (25 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general, lugnet.admin.general)
| | | | | Re: Newsgroup for this (was Re: The Bricktionary project)
|
| (...) Steve, I totally agree what is needed is a complete classification/taxonomy system so you can find a part. The naming component is useful and interesting but this project should be a parts database not just a name database. If the (...) (25 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general, lugnet.admin.general)
| | | | | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
| (...) Personally I prefer Gary Istoc. ;-) [f-up set to lugnet.off-topic.fun] -Tom McD. when replying, spamcake roping has just been outlawed by the Montana Rodeo Commission. (25 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general, lugnet.off-topic.fun)
| | | | | New Palm Tree (was: Re: Another part variation)
|
| (...) Aren't they horrible? The new tree would be somewhat defensible if it held together. But it's more fragile than the old multi-part trees. One step backward, and two steps back. Steve (25 years ago, 8-Jul-99, to lugnet.cad.dev, lugnet.general)
| | | | | Re: The Bricktionary project (Was: Idea: How starting ... Lego piece naming convention?)
|
| (...) Great. I'd love to contribute to the Lugnet Bricktionary in any way possible. Of course, I'd love to contribute to just about any effort to establish a public db for part identification and reference. Steve (25 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
| | | | | Re: Newsgroup for this (was Re: The Bricktionary project)
|
| (...) Sounds good. Right place in the hierarchy. (...) And it's not actually part names, but a parts identification database, right? Having standard/prefered names is good, but it's the pictures (and maybe schematics) that actually identify the (...) (25 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general, lugnet.admin.general)
| | | | | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
| Doesn't seem like they were hidden to me. Just go to "www.lugnet.com", then click on the "Set Inventory Repository" link under "Links & Resources" at the left side of the page, and then select the "800 Town, Train, and other sets inventoried by Tim (...) (25 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
| | | | | Newsgroup for this (was Re: The Bricktionary project)
|
| This seems like it is reaching critical mass (a good thing) and perhaps at this point a dedicated newsgroup should be created for this (i.e., efforts to standardize parts nomenclature). How does lugnet.db.brictionary sound? I wouldn't quite put it (...) (25 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general, lugnet.admin.general)
| | | | | Re: The Bricktionary project (Was: Idea: How starting ... Lego piece naming convention?)
|
| (...) Oops -- I think there has been a major misunderstanding; that's not what I meant at all. When I wrote: TSL> As they say in Canada, Minnesota, and Maine, "O-ya, it's been parta da TSL> plan since day one." :-) Lots of little prototypes and (...) (25 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
| | | | | Re: Another part variation
|
| (...) Plant those new hurricane proof palm trees! Just kiddin', just the other day I had the new tree in my hands for the first time. Yuck. Julie (25 years ago, 8-Jul-99, to lugnet.cad.dev, lugnet.general)
| | | | | Another part variation
|
| obPartTrivia: Anyone notice that there are[1] two different versions of the "Palm Tree Trunk Segment"? One is 40LDU[2] tall, the other is 44LDU tall. The difference is in the male connector on the bottom of the part. The shorter version appears to (...) (25 years ago, 8-Jul-99, to lugnet.cad.dev, lugnet.general)
| | | | | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
| (...) I guess it looks fine with a "K"Gary Istok (...) (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?
|
| (...) And don't forget to include the folks in the Upper Penninsula of Michigan or Yoopers as they are called. "Dey talk like dat too". (...) I like it! Especially without a "K". John Matthews brought up an interesting point about not calling (...) (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?
|
| (...) Ok, I could go with: 1x2 45 degree slope, half pyramid Here's an attempt at the rest of the more or less normal slope parts: 1x2 45 degree slope 2x2 45 degree slope 3x2 45 degree slope (3) ... 1x2 45 degree slope, peak 2x2 45 degree slope, (...) (25 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
| | | | | Re: The Bricktionary project (Was: Idea: How starting ... Lego piece naming convention?)
|
| [Followup-To set to lugnet.admin.database -- can we please corral this (important) discussion to one location? It's getting cross-posted to too many ng's] (...) I've got some LDraw-to-AucZILLA cross-reference information. Let me dig it out... (...) (...) (25 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
| | | | | Re: The Bricktionary project (Was: Idea: How starting ... Lego piece naming convention?)
|
| (...) lists (...) lot (...) Two other resources come to mind: Lutz Uhlmann's Parts Reference at: (URL) reference of technic parts at: (URL) of these cover lots of parts not done in LDraw, and the Technica pages even have images of parts not LDrawn. (...) (25 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
| | | | | The Bricktionary project (Was: Idea: How starting ... Lego piece naming convention?)
|
| Hello everybody, In an earlier post in this thread I stated that I would start to make a list containing the various names for each LEGO part. As many parts have different names in different auctions, programms and inventories it is sometimes hard (...) (25 years ago, 8-Jul-99, to lugnet.admin.database, lugnet.cad, lugnet.cad.dev, lugnet.db.inv, lugnet.general)
|
|
