To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.devOpen lugnet.cad.dev in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / 2258
2257  |  2259
Subject: 
Re: Idea: How starting to work for a unique Lego piece naming convention?
Newsgroups: 
lugnet.cad.dev, lugnet.general
Date: 
Wed, 7 Jul 1999 07:15:27 GMT
Viewed: 
1829 times
  
In lugnet.cad.dev, Todd Lehman writes:
In lugnet.cad.dev, Robert Munafo writes:
It would be bad to put each image on a seperate web page.

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:
http://www.lugnet.com/ldraw/parts/?c=7&n=3004

* A bunch of pieces in a numeric range:
http://www.lugnet.com/ldraw/parts/?c=7&n1=3000&n2=3009

* A bazillion pieces:
http://www.lugnet.com/ldraw/parts/?c=7&n1=0&n2=99999


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 almost useless as a catalog.

Not at all.  In fact, if none of the images were ever on their own page, then
that would also make the resource almost useless.  People often want to be
able to point to a single image of a piece when they're talking about it.

There really needs to be multiple types of displays.


Even if you aren't printing, think how much work it would be to
click-click-click through all the images on the site.

The single-element-on-a-page view is best for when someone points you there
to a specific piece.  A catalog view should show lots of pieces on a single
page, with varying ways to collate them.


Of course, I'm not opposed to adding additional pages so that people can
access the data in different ways. Just make sure you don't eliminate the
format we have now.

Ahh, I should've read this first before writing the above...  :)

--Todd
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 would be confusing to say "this is the part, but actually it is
red" - thinking here of torsos mainly, which can look unrecognisable in an
alien colour. Indeed some parts demand this - eg. black castle parts with grey
decoration.

Also, complex decorated parts (heads, torsos) could benefit from being rendered
at greater than 100% (with some annotation?)

Chris



Message has 3 Replies:
  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)

Message is in Reply To:
  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)

80 Messages in This Thread:































Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR