 | | Gryphon Bricks (Mac) -> LDraw database
|
|
I've put together a few pages with an inventory of the Gryphon Bricks parts, and attempted to cross-reference them with LDraw pieces from Steve Bliss' site. Take a look at: (URL) is a first pass: there are some mistakes here and there, and quite a (...) (25 years ago, 9-Feb-00, to lugnet.cad, lugnet.db.brictionary)
|
| |
| | Re: Online LEGO Inventory Database
|
|
(...) Yep. (...) Oh, and each description should probably be tagged with a source. That way, when we change the description of some part in LDraw, the cross-reference database can be updated. (...) Yep. A better approach may be modeling a set of (...) (25 years ago, 9-Feb-00, to lugnet.db.brictionary)
|
| |
| | Re: Online LEGO Inventory Database
|
|
(...) collate. (...) Yep. The difficulty is in matching up the descriptions from the various sources (e.g. which LDraw part is this Technica part?). Sometimes it's easy, somethimes it's not. (...) Yep. (...) part (...) a (...) and (...) That's the (...) (25 years ago, 9-Feb-00, to lugnet.db.brictionary, lugnet.db.inv)
|
| |
| | Re: What words describe the Lego elements?
|
|
(...) went in and updated the description parameters to include a count of holes in the piece. So if you see the page before I've updated the page with a new image, just pretend there's a hole-count category, OK? Thanks again. Billb. (25 years ago, 9-Feb-00, to lugnet.db.brictionary)
|
| |
| | Re: What words describe the Lego elements?
|
|
(...) From the discussion so far, I can tell that some of us may be confusing a classification system with being able to identify a Lego element. In the perfect database, the inquiry about a piece would not need to know *anything* about how the data (...) (25 years ago, 9-Feb-00, to lugnet.db.brictionary)
|
| |
| | Re: Online LEGO Inventory Database
|
|
(...) 'The database' should allow multiple descriptions per piece. And should have the major descriptions pre-loaded. The core element table should have an abstract key value, and a pointer to a graphic image for each part. A second table, call it (...) (25 years ago, 7-Feb-00, to lugnet.db.brictionary, lugnet.db.inv)
|
| |
| | Re: The Lepanadat Project (update 1)
|
|
(...) Of course you can use the database I'm working on now for a set inventory. Creating a set inventory was also one of my goals when I started with the Lepanadat project, but it takes a lot of time, so it would probably take many, many years (...) (25 years ago, 7-Feb-00, to lugnet.db.brictionary, lugnet.db.inv)
|
| |
| | Re: Online LEGO Inventory Database
|
|
(...) One problem we have at the moment is that the various sources of parts lists (LDraw, Tim Vattima's set inventories, Auczilla, Technica, etc) all contain different subsets of the full parts list and use different descriptions. We need to (...) (25 years ago, 7-Feb-00, to lugnet.db.brictionary, lugnet.db.inv)
|
| |
| | Re: Online LEGO Inventory Database
|
|
(...) I (...) to (...) Perhaps (...) be (...) Sounds good to me! I'm going to begin by designing the database to hold the data, and deciding on the best method to catalog the parts, or the best existing database to use for the parts. Any suggestions (...) (25 years ago, 7-Feb-00, to lugnet.db.brictionary, lugnet.db.inv)
|
| |
| | Re: What words describe the Lego elements?
|
|
(...) It was... 2 letters off is less than 10% margin of error, which is good enough when you're estimating. :-) Are you sure there isn't an umlaut or AE joined or something in his last name? :-) (25 years ago, 5-Feb-00, to lugnet.db.brictionary)
|
