 | | Re: What words describe the Lego elements?
|
|
(...) Nope, "Linnaeus" is spelled correctly. However if the "A" above refers to his first name that's wrong, his first name is Carolus. If not, nevermind. -Chris (25 years ago, 5-Feb-00, to lugnet.db.brictionary)
|
| |
| | Re: What words describe the Lego elements?
|
|
(...) Respectfully disagree. Animals are all related (1), and the nomenclature, driven by the Linnaeus classification system, reflects that relationship. Lego elements, except in limited cases, are not related to each other by derivation or (...) (25 years ago, 4-Feb-00, to lugnet.db.brictionary)
|
| |
| | Re: What words describe the Lego elements?
|
|
After thinking about this a lot, I think we need a nomenclature that is similar to the binomial nomenclature that they use for animals. These could be coupled to a standard name, such as lupus wilus, aka Wiley Coyote. The technical name would allow (...) (25 years ago, 4-Feb-00, to lugnet.db.brictionary)
|
| |
| | Re: The Lepanadat Project (update 1)
|
|
I will be creating a set inventory database, with a web-based searchable interface, and will be, of course, needing some way to refer to each of the parts int he inventory. I would like to put your database online also, in a searchable format, and (...) (25 years ago, 4-Feb-00, to lugnet.db.brictionary, lugnet.db.inv)
|
| |
| | Re: What words describe the Lego elements?
|
|
(...) I had also thought about this subject. One of the names that also should appear in the Lepanadat project is some sort of systematic name. This would allow people to find a picture of the piece and the various names for the piece. I had a few (...) (25 years ago, 4-Feb-00, to lugnet.db.brictionary)
|
| |
| | Re: The Lepanadat Project (update 1)
|
|
It has been a while since I updated the page for the last time. Because I found a new job and had to move, I lately had not very much time over. I also still had to do many things for my own collection, so the Lepanadat project was somewhat on the (...) (25 years ago, 4-Feb-00, to lugnet.db.brictionary)
|
| |
| | Re: What words describe the Lego elements?
|
|
(...) Or "How good a missile is it to throw at my kid brother?" Both are hard to quantify, don't you think? I'm sure neither question will be asked by my version of the brictionary. I do have a small JPG file of the MS Access display of (...) (25 years ago, 4-Feb-00, to lugnet.db.brictionary)
|
| |
| | Re: What words describe the Lego elements?
|
|
(...) A common piece of information, that many neophytes could supply: "How much does it hurt when you step on the piece barefoot?" Steve (25 years ago, 2-Feb-00, to lugnet.db.brictionary)
|
| |
| | What words describe the Lego elements?
|
|
One of the tasks of the bricktionary is to allow the identification of an in-hand Lego element. The user would supply various descriptor words based on what he sees of the object in front of him. What might then happen is a sort of expert system (...) (25 years ago, 2-Feb-00, to lugnet.db.brictionary)
|
| |
| | Re: The Lepanadat Project (update 1)
|
|
Mike, I have consolidated Margo's castle/pirate inventories into one file with the fields Set Number, Quantity, Part Description, and Colour. I could extract a list of unique contents of Part Description as well, and I'm working on adding the field (...) (25 years ago, 26-Jan-00, to lugnet.db.brictionary)
|
| |
| | Re: The Lepanadat Project (update 1)
|
|
If I can get somebody to get the nomenclature down, I will offer to set up a database that will accept the inventories. I was starting on that same project, but it was indeed too immense for me to do alone. I would really like to see an updated (...) (25 years ago, 26-Jan-00, to lugnet.db.brictionary)
|
| |
| | Re: The Lepanadat Project (update 1)
|
|
Has anyone heard anything more about this project? The site has apparently not been updated since the 22nd of September 1999. In the absence of any substantive news, I have embarked on my own consolidation of piece descriptions and image files. It (...) (25 years ago, 26-Jan-00, to lugnet.db.brictionary)
|
| |
| | Element Count Trivia
|
|
"2,172 is the total of different moulded elements in 1999. There are 97 LEGO PRIMO elements, 399 LEGO DUPLO elements, 157 LEGO SCALA elements, 903 LEGO SYSTEM elements, 357 LEGO TECHNIC elements and 137 LEGO DACTA elements – and that’s not counting (...) (25 years ago, 1-Jan-00, to lugnet.faq, lugnet.db.brictionary, lugnet.general, lugnet.cad.dev)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) Yah. Keeping my _sed & awk_ and _Programming Perl_ within reach isn't a matter of life and death -- it's much more important than that. But make is really a simple tool. I wonder just how useful an entire book for it would be. The last one I (...) (25 years ago, 8-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray, lugnet.off-topic.geek)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) Oh, I dunno about O'Reilly... :-) Their stuff is spotty. It varies from good, up through Insanely Great, all the way to YOU CAN'T LIVE WITHOUT THIS BOOK. I wish they'd just pick a quality level and stick to it. :-) (25 years ago, 7-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
Steve Bliss wrote in message ... [ ... snip ... ] (...) There is a very good Make book available from O'Reilly & Associates, _Managing Software Projects with Make_. I have found that this book always seems to have an example for something I was (...) (25 years ago, 7-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) I'm not sure I want to do them all (though the list was much shorter than I thought it would be), but here's a start, the very first on the list. Here are the sets (that I know of) released since 1992, with black 1x1 bricks, sorted reverse on (...) (25 years ago, 5-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) Todd and Joshua D. have an amazing number inventoried, between them. At least that's my suspicion. It's convincing them to make the data available in a format I can run reverse queries against that is the hard part. (25 years ago, 4-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) lugnet.general? lugnet.helpwanted? The current problem is that there aren't that many published inventories for current sets. So you need to hook up to someone who is A-R enough to inventory everything themselves,. Steve (25 years ago, 3-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) I'm going to need to keep a vanilla installation, just for partsref generation. It's too tempting to make minor edits to part files in my regular installation. And, if I'm going to have two copies of LDraw, I'd rather have "working" and (...) (25 years ago, 3-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
[should've snipped the ng list, but I didn't--couldn't decide which to keep/exclude] (...) So, as both the new Keeper of the LDraw Library and the Keeper of the Partsref Pages, I could build a make, and apply it everytime I get new candidate files (...) (25 years ago, 3-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
I haven't gotten any nibbles, can someone suggest a group better suited to answering this question? (...) <for one part> (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) This is kludgy but might work. Details left as an exercise. Your problem is that what you want is to know when a file is *new to YOU* not what it's timestamp is. Keep two complete sets of .dat files. One is an image of the state of files, but (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) You could try the version which comes with Cynwin32: (URL) used Beta 20.1; it seems pretty stable. If you're not too keen on using the Unix sub-layer (slow), try dmake: (URL) it seems to have gone commercial -- you have to *pay* for the (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) Yep, I'm familiar with make. I even went to look for one once. Do you know how hard it is to search the net for 'make'? I never could figure out a decent set of search-words... Oh, wait. I've got a make.exe with my old copy of Turbo Pascal. (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) Are you familiar with the make utility? It allows you to describe an arbitrary set of modules, with their associated interdependencies, and then re-build only the modules which have changed and modules dependant upon them. Of course, using (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) That's fine with me. The only downside is applying updates. When new parts are released for LDraw, I don't update individual partsref images and pages, I just regenerate the whole shebang. So any manual edits would probably get overwritten. (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) Yeah I was thinking that the third size should be a composite of four views top, left, bottom, and right. Should the floor be kept in this kind of view? Ie: Rotate Part over floor rather than 4 Cameras, nuking the floor only on the bottom (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
Excellent! After looking at them I think that other perspectives are more important than colors. Have you tried experimenting with the ambient light option in povray? I don't think l3p gives you that option but you can modify the pov files l3p (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) I Started this Several Weeks ago, I have already run Pov-Ray for the Thumbs and the Large Size. I have only the two sizes done so far. What would you call normal Size, I had not figured out a good third size any suggestions? All pngs, 128x96 (...) (25 years ago, 2-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) Speaking of which... I just posted my wants list. I want hundreds of most of the items on it. Someone pointed out to me that if I could tell of sets that had large quantities of the parts I might get better responses. Given the current state (...) (25 years ago, 1-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
One thing I noticed with the DAT explorer is that POV rendered images look _MUCH_ better with the lossless PNG format thatn with JPEG. Perhaps appropriate use of the JPEG smoothing function would help the the tests I did looked bad even at 100% (...) (25 years ago, 1-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) IMHO, the best thing is having both (a) super-quick-loading GIFs and (b) high-quality POV JPEGs, and then letting the user decide which one to view. A while back, someone even suggested having spinning/rotating POV-rendered images for each (...) (25 years ago, 1-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary, lugnet.cad.ray)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
Kevin Loch <kloch@opnsys.com> wrote in message news:FM32ur.BwF@lugnet.com... (...) I agree. Some parts--especially those with lots of rounded surfaces--can be hard to make out in LDraw. POVRAY works much better for these parts (and for decorated (...) (25 years ago, 1-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) Cool! (...) Is there any desire to have povray rendered images for each part? I still think that would be cool, even though the ldraw versions are more useful for some things. It would also be nice to be able to either: 1. have all parts (...) (25 years ago, 1-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | Re: Partsref is Moving to LUGNET
|
|
(...) Well, like it says on the page, "To reference a part image, when you already know the LDraw number for that part, use the following URL format. (URL).gif" In other words, linking directly to these images is OK in this case. (...) These are (...) (25 years ago, 1-Dec-99, to lugnet.cad.dev, lugnet.db.brictionary)
|
| |
| | Re: Looking for pieces to trade at the meeting (November and Dece mber )
|
|
Not to nit pick too much, but I feel we would be helped if we standardized the terms a bit. I think that there are some elements that are referred to differently than "industry standard" that I have commented on. If I can get to the Decemer meeting, (...) (25 years ago, 30-Nov-99, to lugnet.loc.us.ca.sf, lugnet.db.brictionary)
|
| |
| | Re: Best way to make parts images?
|
|
(...) Quick and Dirty: - Install LDLite and LDraw Add-On - Point LDAO at LDLite for catalog-images (see (URL)). - Run the Make Catalog repeatedly, once for each color. - After running each color-batch, copy/convert all the files in ldraw\vec\ to a (...) (25 years ago, 29-Nov-99, to lugnet.db.brictionary, lugnet.cad)
|
| |
| | Re: Best way to make parts images?
|
|
(...) I once wrote a program to create GIFs from the LeoCAD library for a person who wanted to build a database with all parts. If you're interested, just tell me how you want the files (size, color, command line options) and I'll recompile it (or (...) (25 years ago, 27-Nov-99, to lugnet.db.brictionary, lugnet.cad)
|
| |
| | Re: Best way to make parts images?
|
|
(...) I don't think I agree. The images produced by LDLITE or something similar contain much more information, as they include the edge-lines in the parts. I tried to use raytraced images for instructions once, but I quickly came to the conclusion (...) (25 years ago, 27-Nov-99, to lugnet.db.brictionary, lugnet.cad)
|
