 | | Re: Best way to make parts images?
|
|
I would use l3p and povray, but since l3p only runs on wintel, you have to do that part on a wintel box. Here's how I would do it: 1. Make a batch file to create a dat file for each part. 2. make a batch file to run l3p on each of those dat files 3. (...) (25 years ago, 27-Nov-99, to lugnet.db.brictionary, lugnet.cad)
|
| |
| | Best way to make parts images?
|
|
What's the "best"[1] automated or semi-automated way to render a large number of parts images into GIFs? (It's OK if there are multiple steps or if a final pass has to convert the results from PNG or BMP to GIF.) What I would like to do for the (...) (25 years ago, 27-Nov-99, to lugnet.db.brictionary, lugnet.cad)
|
| |
| | Re: Inventories
|
|
(...) Well, it's not trying to yet...that part is still a ways out. (...) Right. That interface was a quick prototype and an experiment to get the feel of cross-referencing hops between different object types. It was never meant as anything but a (...) (25 years ago, 10-Oct-99, to lugnet.general, lugnet.db.inv, lugnet.db.brictionary, lugnet.admin.database)
|
| |
| | Re: Inventories
|
|
(...) Well, there are several reasons I am not going to do that. First off is that I know how to program Access. Those who know how to program other systems have not put forth the time to make one in their programming language of choice, so I will (...) (25 years ago, 10-Oct-99, to lugnet.general, lugnet.db.inv, lugnet.db.brictionary)
|
| |
| | Re: wishing upon a star
|
|
(...) Har! No, really...you brains good and my bad and me grammar good too! I got exactly what I wanted...a flurry of responses, in a simple endeavor to find out if the best and brightest have come up with any solutions to a part search and (...) (25 years ago, 27-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: wishing upon a star
|
|
(...) c /here/hear/ ... but who's here to notice? (...) Swelled heads typically occur when new facts are uttered. Nothing was by Dave that I didn't already know to be true about myself so there's no danger of (additional) swelling. But seriously, I (...) (25 years ago, 27-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: wishing upon a star
|
|
In lugnet.db.brictionary, Dave Lovelace writes: [SNIP] (...) ...you are all truly brilliant, and obviously experienced, (...) Please don't let Lar here this! His head is quite large enough already.... :^) as evah, John C. (25 years ago, 27-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: wishing upon a star
|
|
(...) Not so fast, my humble friend... Just because it isn't used as the database key or as the "unique definitive" part number doesn't mean your part numbers have no merit. I supported your suggestion because I felt it was appropriate to include a (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: wishing upon a star
|
|
(...) It sounds like you're talking about the mold quality control numbers. On most LEGO parts that a large enough concealed surface, you find three numbers -- two vary from part to part for the reasons you describe. These are usually one or two (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: wishing upon a star
|
|
(...) Thank you for the kind words, John...and the insights. I am a two-month old "newbie" and have very little to offer gods of thinking such as yourself, and also of course the other geniuses involved in this discussion, other than simple hero (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary)
|
| |
| | RE: wishing upon a star
|
|
Let me add my support to this as well. Make the key be some arbitrary unique number. I've been programming for about 17-18 years, and in the early days I would have disagreed. Experience has proven otherwise. --- Dave Hylands Email: (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: OID generation (was: Re: wishing upon a star)
|
|
(...) Quick answer: yes. Long answer: Almost certainly. There are some tradeoffs that you've made. A big one is around the human readability of the key. Ask yourself, how often do humans inspect these, and how fast can you convert back to 40bit (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary, lugnet.off-topic.geek)
|
| |
| | Re: wishing upon a star
|
|
(...) For anyone that might not know this, Mold numbers are not unique. A mold is setup for all the parts and it makes more than 1 piece at a time. If you take the 2x4 brick mold, it could possibly do 8 bricks at a time which means each brick in the (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary)
|
| |
| | OID generation (was: Re: wishing upon a star)
|
|
(...) Lar, I've been experimenting with a method for OID construction which takes a pseudorandom 32-bit integer, converts it to a 40-bit integer by adding 8 bits of CRC, then converts that an to 8-byte base-32 ASCII representation using the 32 (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary, lugnet.off-topic.geek)
|
| |
| | Re: wishing upon a star
|
|
(...) It's known to be not unique, there's a many-to-many relationship between TLG numbers and unique mold-forms. That is, the same number has been used for different parts (at least, different versions of parts), and different numbers have been (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: wishing upon a star
|
|
(...) Whoops. Talking in shorthand tripped me up. In system-architect-speak "business" logic is the actual desired work effort of the program (contrasted with non business logic which is the infrastructure or other code that you have to do in order (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary, lugnet.off-topic.geek)
|
| |
| | Re: wishing upon a star
|
|
In lugnet.db.brictionary, Dave Lovelace writes: [SNIP] (...) Well, not so fast. All ideas are welcome here. Maybe a larger perspective might help. I understand the frustration of an ignoramus coming to LEGO parts naming and numbering. I've been (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: wishing upon a star
|
|
(...) Pardon my inexperience. I am neither a program designer, nor a person with any business logic whatsoever...perhaps I should have footnoted these factss before sticking my idea out here. I think that 90% of the users of a would-be (...) (25 years ago, 26-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: wishing upon a star
|
|
(...) Precisely. It's not guaranteed to be unique and it has business meaning. Now, clearly, the underlying DB implementation should index on that column because we are likely to be doing a lot of lookups, but that is an optimization/implementation (...) (25 years ago, 25-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: wishing upon a star
|
|
(...) Taking that to the ultimate suggests even the TLG part number should not be the key (which of course is already a known issue if you want to account for color and/or printing). (25 years ago, 25-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: wishing upon a star
|
|
Yes, indeed, John is (as evah) right. Let me weigh in here as well... Putting meaning in keys is a sign of not very well seasoned designers, IMHO. A pretty strong principle of database design is NOT to let your key have business meaning. Get keys (...) (25 years ago, 25-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: wishing upon a star
|
|
Hi guys, I would urge caution on the creation of complex codes to identify pieces. I admit, I am prejudiced. I worked on a database management project back in the early 80s for a water-quality study in which water samples were identified with a (...) (25 years ago, 25-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: wishing upon a star
|
|
Hi Dave & Robert, Robert Munafo <munafo@gcctechNO.SPAMcom> wrote in message news:FGzv17.4G8@lugnet.com... (...) bricks. (...) the (...) one of (...) I like this idea. I think we could use the rest of the digits to identify the piece more accurately. (...) (25 years ago, 25-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: wishing upon a star
|
|
(...) I like this system, but just want to comment that it's not a complete substitute for the part numbers that LEGO molds on the bottom of the bricks. Another issue is that there are an awful lot of parts that don't fall into the category of (...) (25 years ago, 25-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: Part 4180
|
|
(...) Yes. :-) It first came with train wheels (it's situated with the train elements) -- 1980; both 2x2 and 3x3, but later (1981?), studded hubs were added. One of many discrepancies the Numbers Group has mentioned to Terry, but which have yet to (...) (25 years ago, 22-Aug-99, to lugnet.db.brictionary)
|
| |
| | Part 4180
|
|
I have a part 4180, but it has car wheels, not train wheels. Isn't part 4180 just the holder? /Tore (25 years ago, 21-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: Question from a newbie
|
|
Hi Craig, The following 3 sites might help you. They give part names, images and (in some cases) numbers: (URL) (for Technic only) (2 URLs) C. In lugnet.db.brictionary, Craig Livingston writes: [SNIP] (...) (25 years ago, 18-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: Question from a newbie
|
|
Hi Craig, Welcome and thanks for posting! Craig Livingston <CLivin007@aol.com> wrote in message news:FGL6HI.JpL@lugnet.com... (...) legos. (...) the (...) and (...) brick-naming (...) nomenclature (...) Yes you did come to the right place (I think (...) (25 years ago, 17-Aug-99, to lugnet.db.brictionary)
|
| |
| | Question from a newbie
|
|
I really don't know if this is right place to post this, but here goes: Since coming out of my own dark ages, I have really gotten involved in legos. I enjoy reading lugnet.com's newsgroups, but often I am unable to decipher the meaning of a brick (...) (25 years ago, 17-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: brictionary request
|
|
(...) Probably not -- unless the output format just happens to work with your program. When a real database of parts does get off the ground (with the ability for people to contribute directly to it in an automated way), I'm almost certain that you (...) (25 years ago, 12-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: brictionary request
|
|
(...) First off, wait and see what the database looks like (it doesn't exist until it's published, right?). Then, *you* can take the time and effort to transport the data from the database into your inventory generator. Stop asking for people to do (...) (25 years ago, 12-Aug-99, to lugnet.db.brictionary)
|
| |
| | brictionary request
|
|
when this massive database of parts gets off the ground does everyone here woorking on it think that they could make a data file (updated regularly) to go with my inverntory generator? all i need in it is part #'s and descriptions (25 years ago, 12-Aug-99, to lugnet.db.brictionary)
|
| |
| | Re: Bricktionary
|
|
(...) Shows me what happens with stale followup-to's... (...) Interesting ideas. Could be useful, especially for parts with no simple description. (...) Steve (25 years ago, 1-Aug-99, to lugnet.db.brictionary)
|
| |
| | The Lepanadat Project (update 1)
|
|
Hello everybody, I've been working on the Lepanadat project (parts names database) for some time now. It doesn't go very fast as I had also much other things to do, so it probably will take some time before it is finished. As I'm leaving Switzerland (...) (25 years ago, 26-Jul-99, to lugnet.db.brictionary)
|
| |
| | Interesting part variation
|
|
I just noticed that the treasure chest (parts 4738 and 4739) comes in two variations. One (which appears older based on the fact that my current sets have the other variation) has a smaller hinge pins and holes. The lid with the smaller pins will (...) (25 years ago, 18-Jul-99, to lugnet.db.brictionary)
|
| |
| | Re: Newsgroup for this (was Re: The Bricktionary project)
|
|
What's this all about? You guys playing hide and seek in here? Adam Steve Bliss <blisses@worldnet.att.net> wrote in message news:3786467b.729193...net.com... (...) (25 years ago, 17-Jul-99, to lugnet.db.brictionary)
|
| |
| | Partsref Updated
|
|
[this should have been a cross-posting with (at least) lugnet.cad.dev, but I forgot to remember it] Finally! I've refreshed the parts-reference pages at (URL). The display is slightly reformatted. Just cosmetic changes, it's still frames-based :( (...) (25 years ago, 16-Jul-99, to lugnet.db.brictionary)
|
| |
| | Re: part database issues I have had to deal with
|
|
(...) will (...) It might be obvious, but I'll just point out that most of those names either come from the technica registry: (URL) from the LDraw image catalog at: (URL) as you can see I rearranged the words to eliminate the awkward use of commas. (...) (25 years ago, 15-Jul-99, to lugnet.db.brictionary)
|
| |
| | Re: The Lepanadat project (Was: Idea: How starting ... Lego piece naming convention?)
|
|
(...) For the moment I will keep the name Lepanadat, otherwise I have to change to change the name in some files again. Also I think there isn't that much people that visit the site at the moment, so the actual name still isn't important. As soon as (...) (25 years ago, 15-Jul-99, to lugnet.db.brictionary)
|
| |
| | Re: part database issues I have had to deal with
|
|
(...) Hello Robert, Thanks for your list and your comments about identification of the pieces. It is very interesting. I have copied the names you used for the parts to my computer and will add them to the names I already have for parts, but that (...) (25 years ago, 15-Jul-99, to lugnet.db.brictionary)
|
