 | | Re: Peeron crosses 2000 inventory mark!
|
|
(...) When exactly did the transition to hollow studs occur? This *can* be cleaned up, sorta (see below), although it's time consuming. A parts database that allowed built-in ambiguity of which part a given inventory has might be a better solution. (...) (22 years ago, 27-Feb-03, to lugnet.db.brictionary, lugnet.pirates)
|
| |
| | Sticker scan for Main Street (Set 6390)
|
|
Does anyone have a scan of the sticker set for the main street lego set? Even scans of the bricks with the stickers already applied would be great. Also, a scan of the men at work sign image would be fantastic if available. Thanks, Karl (22 years ago, 17-Feb-03, to lugnet.db.scans)
|
| |
| | Re: Proposal: New Part Numbering System
|
|
(...) ...snip. Well I consider a common parts numbering system to be totally nessesary. I have spent the last 4 months counting and cataloging my collection. For the most part I have used LDraw number because that was what I had first. I have to (...) (22 years ago, 14-Feb-03, to lugnet.cad.dev, lugnet.db.inv, lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part Numbering System
|
|
(...) The question has been asked before, I believe it will be asked again. The general reason that a corporation would not cooperate in a situation like is that it would cost them money (ie, they'd have to pay people to spend their time dealing (...) (22 years ago, 14-Feb-03, to lugnet.cad.dev, lugnet.db.inv, lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part Numbering System
|
|
(...) I agree. Ask the question first, explain the benefit to the community, and hope for the answer we are looking for. It would seem to me that if the information is available on larger parts for public consumption, surely they would not maintain (...) (22 years ago, 13-Feb-03, to lugnet.cad.dev, lugnet.db.inv, lugnet.db.brictionary)
|
