|
|
 | | 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)
|
|
