 | | 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.
|
|
(...) 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.
|
|
(...) 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.
|
|
(...) 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)
|
| |
| | Official LEGO Color Chart
|
|
Thanks to Jake and TLC, we just posted an official LEGO color chart, with RGB, CMYK, and Pantone colors, and a danglish name! Take a look: (URL) will be working in the next few weeks with LDraw to associate each of these colors with our current (...) (21 years ago, 30-Aug-03, to lugnet.announce, lugnet.cad, lugnet.db.brictionary, lugnet.cad.dev, lugnet.cad.ray) !!
|
| |
| | Re: Part 4318
|
|
I'm guessing the centered tab under the two fingers was counted as the third finger. IIRC, it functions not as most hinge "fingers" do, but stops the attached part from moving lower than horizontal. (...) (21 years ago, 28-Apr-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: Part 4180
|
|
(...) I thought I remembered a more recent discussion about this, but I can't find it. What I'm seeing is that really instead of the current part 4180 there should be three composite parts: 4180c01--Brick 2 x 4 with Permanent Black Train Wheels (...) (21 years ago, 20-Mar-03, to lugnet.db.brictionary, lugnet.cad.dat.parts)
|
| |
| | Part names: describe shape, not what models they come in
|
|
There are a number of parts that are named according to their use in a particular set. Trouble is, LEGO would then come out with another set that uses that part in a totally different way. Consider "Loudhailer." That one took me forever to find in (...) (21 years ago, 12-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)
|
| |
| | Part 4318
|
|
This part (URL) called Hinge Boat Mast with 3 Fingers On Both Sides despite seeming to have two fingers on each side, like (URL) it misnamed, or am I missing something? TIA, -- TWS Garrison (URL) capital letters in address for direct reply. (21 years ago, 8-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.
|
|
(...) Excellent idea. --Todd (21 years ago, 7-Mar-03, to 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)
|
| |
| | 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)
|
| |
| | 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 (...) (21 years ago, 14-Feb-03, to lugnet.cad.dev, lugnet.db.inv, lugnet.db.brictionary)
|
