 | | Re: Idea: How starting to work for a unique Lego piece naming convention?
|
|
(...) 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?
|
|
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?
|
|
(...) 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?
|
|
(...) 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?
|
|
(...) 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?
|
|
(...) 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?
|
|
(...) 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)
|
|
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)
|
|
(...) 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)
|
|
(...) 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)
|
|
(...) 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)
|
