 | | Re: Idea: How starting to work for a unique Lego piece naming convention? —Steve Bliss
|
| | | (...) Are you having problems with the pages I put up at (URL)? Do you have any suggestions on ways the pages could be restructured to be smaller, but still usable as a tool to locate a specific part by looking at images of a bunch of parts? Some (...) (25 years ago, 6-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| | | |
| | | | | Re: Idea: How starting to work for a unique Lego piece naming convention? —Frank Filz
|
| | | | | (...) Actually it was Lutz Uhlmann's Part Reference (at (URL) Frank Filz ---...--- Work: mailto:ffilz@us.ibm.com Home: mailto:ffilz@mindspring.com (25 years ago, 6-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| | | | | |
| | | | | Parts Database (Was: Idea: ... Lego piece naming convention?) —Tore Eriksson
|
| | | | | So far, I've only used LDraw's partlist and Lutz's, but I must say Steve's looks very promising. When it comes to Lego databases, there is an infinite amount of data we all wish to enter or seek on. Here's my two ideas to make Mission Impossible a (...) (25 years ago, 6-Jul-99, to lugnet.general, lugnet.cad.dev)
|
| | | | | |
| | | | | | | Re: Parts Database (Was: Idea: ... Lego piece naming convention?) —Martin Legault
|
| | | | | | (...) Hi all A standard naming convention is defenetively a must, weither Ldraw or Aucxilla or what ever it is, my self, I build a db for part inventory giving my own Part Number, Description and it is confusing with all the part auction around. In (...) (25 years ago, 6-Jul-99, to lugnet.general, lugnet.cad.dev)
|
| | | | | | |
| | | | | Re: Parts Database (Was: Idea: ... Lego piece naming convention?) —Tim Courtney
|
| | | | | (...) EXCELLENT IDEA, Tore! Having that searchable would help a lot. Though it seems an odd characteristic to include, and no one would permanently categorize a piece by number of studs ('cept bricks, plates, and tiles), it is very helpful in (...) (25 years ago, 6-Jul-99, to lugnet.general, lugnet.cad.dev)
|
| | | | | |
| | | | | | | Re: Parts Database (Was: Idea: ... Lego piece naming convention?) —Anders Isaksson
|
| | | | | | Tim Courtney skrev i meddelandet <4.2.0.58.1999070617...mm.com>... (...) Don't forget LDLIST, (URL) can search the LDRAW parts on any text in the description, CATEGORY and KEYWORDS, and show a picture of the parts found. (And I can modify it if (...) (25 years ago, 6-Jul-99, to lugnet.general, lugnet.cad.dev)
|
| | | | | | |
| | | | | | | | Re: Parts Database (Was: Idea: ... Lego piece naming convention?) —Steve Bliss
|
| | | | | | (...) Definitely don't forget LDList! It's a great tool for finding parts. :) Steve (25 years ago, 7-Jul-99, to lugnet.general, lugnet.cad.dev)
|
| | | | | | |
| | | | | Re: Idea: How starting to work for a unique Lego piece naming convention? —Robert Munafo
|
| | | | | (...) It would be bad to put each image on a seperate web page. Right now I depend on printed parts catalogs, and having all the images on one page allows me to print them out quickly. If the parts were each on their own page it would make the site (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| | | | | |
| | | | | | | Re: Idea: How starting to work for a unique Lego piece naming convention? —Todd Lehman
|
| | | | | | | (...) Correction: it would be bad to put each image *only* on a separate web page. Right? It really needs both (or multiple) types of displays. Here are a couple of crude, semi-working examples... * One piece: (URL) A bunch of pieces in a numeric (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| | | | | | | |
| | | | | | | | | Re: Idea: How starting to work for a unique Lego piece naming convention? —Frank Filz
|
| | | | | | | | | Todd Lehman wrote in message ... (...) problem... in the above database, part 3002 is a 2x3 brick, part 3002PEYE is a 2x2 brick with printing of an eye). Frank (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| | | | | | | | | |
| | | | | | | | | | | Re: Idea: How starting to work for a unique Lego piece naming convention? —Terry Keller
|
| | | | | | | | | | (...) Speaking of which, that 3002peye is one of those early mistakes that needs to be fixed. -- Terry K -- (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| | | | | | | | | | |
| | | | | | | | | Re: Idea: How starting to work for a unique Lego piece naming convention? —Chris Dee
|
| | | | | | | | | (...) Would the plan be to include images for each part in each known colour? For the decorated parts, at least, I would prefer that the image uses a real life background colour rather than the default grey. As a reference for parts sales, etc it (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| | | | | | | | | |
| | | | | | | | | | | Re: Idea: How starting to work for a unique Lego piece naming convention? —Tore Eriksson
|
| | | | | | | | | | | (...) Why not add some new meta-commands? Either: 0 DEAFULTS COLOUR=15 ZOOM=150 (or 1.5) Or: 0 DEFAULT COLOUR 15 0 DEFAULT ZOOM 1.5 ... In fact, parts of the database could be hosted in the parts' .DAT files (to be continued in my posting subjected (...) (25 years ago, 7-Jul-99, to lugnet.general, lugnet.cad.dev)
|
| | | | | | | | | | | |
| | | | | | | | | | | Re: Idea: How starting to work for a unique Lego piece naming convention? —Frank Filz
|
| | | | | | | | | | | (...) One neat thing that can be done if the pictures are served up by a cgi script is to store only a single image, but go in and modify the color before shipping it out. Of course you would need a standard set of color names, and a syntax for (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| | | | | | | | | | | |
| | | | | | | | | | | Re: Idea: How starting to work for a unique Lego piece naming convention? —Steve Bliss
|
| | | | | | | | | | (...) I hope not. That would limit the site to serving up images in predefined colors. Two bad results: the list of predefined colors could become outdated, and some people might have a reason for making up their own color values for parts. I'd (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| | | | | | | | | | |
| | | | | | | | | Secret LUGNET areas, ldraw image databases, (was piece naming conventions) —Robert Munafo
|
| | | | | | | | Gee, thanks Todd -- I didn't even know about (URL) there is no link to it from the LUGNET home page! How many other secret LUGNET pages are there? Concerning the parts image database it looks like we agree, and a good start would be to combine the (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| | | | | | | | |
| | | | | | | | | | Re: Secret LUGNET areas, ldraw image databases, (was piece naming conventions) —Todd Lehman
|
| | | | | | | | | (...) That's actually an obsolete URL, back from when some various options were being looked at for how to partition the .cad.dat ng hierarchy. Some of the data is left behind there, so the new code formats it the new way. I'll go wipe that (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| | | | | | | | | |
| | | | | | | | | | Re: Secret LUGNET areas, ldraw image databases, (was piece naming conventions) —Jeremy H. Sproat
|
| | | | | | | | (...) You might also note that, from the main page, finding these two is something of a challenge: (URL) - jsproat (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| | | | | | | | |
| | | | | | | | | | Re: Secret LUGNET areas, ldraw image databases, (was piece naming conventions) —Todd Lehman
|
| | | | | | | | (...) If those pages were too easy to find, it would intimidate people. No one wants to get their feet wet at a site when they think they have to register first to do anything. Note that there are so many sites out there that make you actually (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general, lugnet.admin.general)
|
| | | | | | | | |
| | | | | | | Re: Idea: How starting to work for a unique Lego piece naming convention? —Steve Bliss
|
| | | | | | (...) OK. I agree with you. The idea behind my site was to help people who are trying to locate hard-to-describe pieces, and need to visually browse through the catalog. (...) Again, I agree. I was just brainstorming ideas on how to reduce the (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev, lugnet.general)
|
| | | | | | |
| | | | | Re: Parts Database (Was: Idea: ... Lego piece naming convention?) —Tore Eriksson
|
| | | | Ah, yet another promising database variant! This is great, and fast! I only see one problem with it is it only includes official LDraw elements. Isn't there any way we could make .DAT files for not yet rendered parts, too? Just for database (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev)
|
| | | | |
| | | | | | Re: Parts Database (Was: Idea: ... Lego piece naming convention?) —Steve Bliss
|
| | | | (...) Creating shell .DAT files is a simple way to record information for parts which haven't been created for LDraw. I wouldn't include these shell files in the L-CAD parts updates, but they would be useful for building a parts-base. (...) That (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev)
|
| | | | |
| | | | | | Re: Parts Database (Was: Idea: ... Lego piece naming convention?) —Steve Bliss
|
| | | | (...) How about a 0 IMAGE meta-command, for those parts which are not-yet coded? That way, we could supply a URL for all parts, and the image could come from any source. Of course, it might make more sense to have that particular item as a column in (...) (25 years ago, 7-Jul-99, to lugnet.cad.dev)
|
| | | | |
