 | | Slope Brick Round
|
|
Following up on a comment by Chris Dee on part 33243 on the Tracker. . . There's this part 500 from the last parts update Slope Brick Round 1 x 6 Inverted The first mysterious thing about this name is that it starts with "slope", but then proceeds (...) (21 years ago, 19-Nov-03, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Re: Fwd from a builder: Colors don't match, among other things!
|
|
(...) This article is a quite interesting read. What jumped out at me was the mention that different colors of ABS have different specific gravities (within a small overall range). I wonder if the saline solution would have a detrimental effect on (...) (21 years ago, 16-Nov-03, to lugnet.general, lugnet.db.brictionary, lugnet.cad, lugnet.market.theory)
|
| |
| | 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)
|
| |
| | Re: 8429 re-release of 8812 not found
|
|
(...) Probably because no one posted about it to lugnet.admin.database. What's with this set? I've never heard of it not that that indicates much), and it's not on shop.lego.com. XFUT lugnet.admin.database (21 years ago, 6-Oct-03, to lugnet.db.brictionary, lugnet.admin.database)
|
| |
| | 8429 re-release of 8812 not found
|
|
Hello all, I have without any result tried to find the 8429 set ((URL)) - a re-release of the 8812 set ((URL)) - in the Lugnet database. Why is it not listed? Best regards, Peter (URL) (21 years ago, 5-Oct-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.
|
|
(...) 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)
|
