To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cadOpen lugnet.cad in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / 10872
10871  |  10873
Subject: 
Re: Lightbricks (x265/x266/x267)
Newsgroups: 
lugnet.cad
Date: 
Fri, 5 Dec 2003 13:07:14 GMT
Viewed: 
602 times
  
Tore wrote:
I protested then, and I protest the same way now. I don't agree with Steve, and
I probably never will. There was *ABSOLUTELY NO NEED* to make three files for
one part like 7930.

"Absolutely" is an exaggeration.  There's a very simple need to put the frame and the
glass in separate files: so modelers can change the colors of both.  Then there's a
simple reason to make a combined file: because, as you said, that's the real part.

With some classic windows, there will even be four files:
one with plain number: nn.dat 0 ~Moved to nnc01.dat, a glass with a new number,
the frame without glass, and nnc01.dat.

Maybe.

Samsonite made windows with glass and frame slightly different from the Denmark
plant. That gives us three new files: a new file for that glass, a new file for
the frame (with hole on top), and a new "complete assembly" file.

That's assuming someone someone models this 'slightly different' part.

But the "complete assembly" *IS* the part.

I totally agree with you there.

That leads to the only reasonable solution: The transperent "part of a part" be
inlined a hard-coded color 47. That makes one part, one file. This is the way
James did (well, not with 35b.dat, but I'm sure he'd put it in the \s folder if
it had existed back then.)

Inlining the glass goes directly against the need to allow modelers to change all
colors.

The second best is to put all subparts to (x265/x266/x267) into parts\s and not
clutter the parts folder with more "theorecically part"

Nope, sorry - if a modeler is likely to interact with a file, that file should go in
parts, not parts\s.  parts\s should be totally invisible to model builders.

That will make straight
part names, too: 265.dat and 266.dat, and free up 267 for a real part.

If we decide to use some single-number naming scheme (like 265, 265s01, 265s02), I'm
fine with that.  Right now, the approach is to use separate numbers.

Allow me to ramble a bit...

In the parts directory, we see these styles of part numbers:

XXXXX   - 4-, 5-, or 7- digit numbers, representing official lego part numbers.
XXX     - 1- to 3- digit numbers, for parts where we don't know the lego number.
XXXXp01 - patterned versions of parts
XXXXc01 - composite part files.  These are either 'complete' parts or 'shortcuts'.
XXXXa   - This is either a version of a part, representing a change in a part over
time, or a part that is delivered from lego on a runner, like the minifig tool wheel.

Right now, we don't have a standard for 'subpart' files, such as window frame &
window glass, using the same number as the complete version of the part.  If we want
to start one, that's fine.  But this is where we're at, today.

Steve



Message has 1 Reply:
  Re: Lightbricks (x265/x266/x267)
 
(...) Like a Gospel preacher once said: "I've shed barrels of tears because of my exaggerations"... :) /Tore (21 years ago, 5-Dec-03, to lugnet.cad)

Message is in Reply To:
  Re: Lightbricks (x265/x266/x267)
 
(...) I protested then, and I protest the same way now. I don't agree with Steve, and I probably never will. There was *ABSOLUTELY NO NEED* to make three files for one part like 7930. With some classic windows, there will even be four files: one (...) (21 years ago, 3-Dec-03, to lugnet.cad)

6 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