 | | 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: Proposal: New Part *NAMING* System.
|
|
In lugnet.cad.dev, William R. Ward writes: <snip> This is a really great idea! In addition, it wouldn't be all that hard to implement into existing software. We'd still have to keep the names in the part files though, to keep backward compatability. (...) (21 years ago, 1-Mar-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
(...) Excellent idea. --Todd (21 years ago, 7-Mar-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
(...) Yep, and programs could still use that if no custom file was available. ROSCO (21 years ago, 7-Mar-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
(...) Thanks! Now how can we get it implemented, is the big question? So now we just need to get all the various parties to the same virtual table as it were. I don't think the MLCAD and BrickLink folks read this forum, do they? --Bill. (21 years ago, 12-Mar-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
(...) I've been also busy cataloging my LEGO collection. I use the master part list downloaded from Peeron as a start. Eventually I found out that especially the decorated bricks and decorated minifigs are missing as a unique part number in the (...) (21 years ago, 11-Apr-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
(...) I like the ideas proposed here. They are almost identical to something I've been tossing around for a while with some other folks. Anyone out there interested in being involved in creating a public catalog ? Ray (21 years ago, 23-Sep-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
(...) We're very interested in having a public system set up, and would love working with one. It's something that we've been planning to do (with LDraw) for quite some time now - we even posted back in the day, to try and get some momentum going, (...) (21 years ago, 23-Sep-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
(...) This is a working draft of what I have in mind - Ray ===...=== Conceptural Outline for a Public Parts Catalog A) The results of the effort will be held under a public content license (such as Open Content or Creative Commons). The results will (...) (21 years ago, 28-Sep-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
(...) Ray - this sounds like a very ambitious (and cool!) project :-) See some questions inline. (...) Why not block some numbers off for natural groupings of parts? Would say, a 1x2 brick with click hinge (2 prongs) and the same with 1 prong (that (...) (21 years ago, 29-Sep-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
Just to through my 2 cents in (even though I'm two weeks behind the rest of this thread ;-) )...I'm definitely interested in being a part of this project. (Being a data-organization junkie may have something to do with it.) Let me know what I need (...) (21 years ago, 13-Oct-03, to lugnet.db.brictionary)
|
