 | | Proposal: New Part *NAMING* System.
|
|
Once the numbering system is in place, we then can deal with the next sticky issue: part names. Since everyone will want their names to be the final name chosen, I would like to sidestep that issue - there should not be a final name chosen. But (...) (21 years ago, 28-Feb-03, to lugnet.cad.dev, lugnet.db.inv, lugnet.db.brictionary)
|
| |
| | Re: LEGO Database Software
|
|
(...) you're describing a feature that we've been thinking of for Peeron.com. Unfortunately, I don't currently have the time to implement it, but it is planned :) Sorry I can't be of more help :/ Dan (21 years ago, 28-Feb-03, to lugnet.db.brictionary)
|
| |
| | LEGO Database Software
|
|
I've been searching for a software program that will let me track my LEGO parts inventory and compare my inventory to the available set parts lists and show me what set I can build. I checked out BrikTrak which does let me enter my parts inventory (...) (21 years ago, 28-Feb-03, to lugnet.db.brictionary)
|
| |
| | 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. (...) (21 years ago, 27-Feb-03, to lugnet.db.brictionary, lugnet.pirates)
|
| |
| | 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 (...) (21 years ago, 14-Feb-03, to lugnet.cad.dev, lugnet.db.inv, lugnet.db.brictionary)
|
