To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.db.brictionaryOpen lugnet.db.brictionary in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Database / Brictionary / 304
303  |  305
Subject: 
Re: Proposal: New Part *NAMING* System.
Newsgroups: 
lugnet.db.brictionary
Date: 
Tue, 23 Sep 2003 00:12:09 GMT
Viewed: 
6368 times
  
In lugnet.cad.dev, William R. Ward wrote:

Once the numbering system is in place, we then can deal with the next
sticky issue: part names.

Since everyone will want their names to be the final name chosen, I
would like to sidestep that issue - there should not be a final name
chosen.  But there should be a small number of 'naming schemes' that
can be used.

Even the basic bricks will have some contention; for example German
AFOL's probably would rather see "Steine 2 x 4" instead of "Brick 2 x
4" as a name.

Imagine a file containing part numbers and names, separated by a TAB
character.  Now imagine another file with a different set of names for
the same part numbers.  Imagine a folder/directory containing many
such files.

MLCAD and Bricklink and Peeron could all have a configuration setting
to let the user pick which file should be used to display the names
for a part.  The user interface would be like that used to select a
"theme" or "skin" in software like Mozilla or WinAmp or Windows
itself.

Each part list would be maintained by someone.  Whenever a new part is
released by LEGO, the maintainers would each update their parts lists
and publish the new version on a website.  Interested parties would
update their lists periodically.

It's a pretty simple system, but it would require a change to several
different programs to use it.  The advantage however is that no one
party can dictate how parts are named, so internationalization or just
vanity customization is possible and even easy.

Now you would never have to remember if it's spelled "tire" or "tyre"
or if it is a "jumper brick" or a "plate 1x2 with center stud" or
whatever.  LDraw users could even create their own names, without
breaking compatibility with anything (since the LDR/MPD file contains
only the part numbers).

Comments?

I like the ideas proposed here. They are almost identical to
something I've been tossing around for a while with some
other folks. Anyone out there interested in being involved
in creating a public catalog ?

Ray



Message has 1 Reply:
  Re: Proposal: New Part *NAMING* System.
 
(...) We're very interested in having a public system set up, and would love working with one. It's something that we've been planning to do (with LDraw) for quite some time now - we even posted back in the day, to try and get some momentum going, (...) (21 years ago, 23-Sep-03, to lugnet.db.brictionary)

Message is in Reply To:
  Proposal: New Part *NAMING* System.
 
Once the numbering system is in place, we then can deal with the next sticky issue: part names. Since everyone will want their names to be the final name chosen, I would like to sidestep that issue - there should not be a final name chosen. But (...) (21 years ago, 28-Feb-03, to lugnet.cad.dev, lugnet.db.inv, lugnet.db.brictionary)  

11 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