Subject:
|
Re: Getting rif off the 8.3 nomenclature???
|
Newsgroups:
|
lugnet.cad.dat.parts
|
Date:
|
Tue, 27 Mar 2007 19:01:24 GMT
|
Viewed:
|
4351 times
|
| |
|
|
In lugnet.cad, Willy Tschager wrote:
> guys,
>
> I'm currently working on 004219b.dat - Sticker System with Australia Flag
> Pattern. unfortunately there is no rule for subparts in the sticker standard:
>
> http://www.ldraw.org/Article339.html
>
> according to the PT references:
> http://www.ldraw.org/library/tracker/ref/numberfaq/
> http://www.ldraw.org/library/tracker/ref/filetypesfaq/
>
> ******************************
>
> How are subparts numbered?
> A: Subparts, which are stored in the \s subdirectory, should bear some
> relationship to their "parent" main part. They are numbered by appending some
> suffix to the part number of the main part, for example 1234.dat might have a
> subpart named s\1234s01.dat and 1234p56.dat might have subparts named
> s\1234p56a.dat or s\1234a56.dat. There is more information on this topic on the
> File Types FAQ page.
>
> ******************************
>
> What are subparts, when should they be used, and how are they numbered?
> A: Subparts may be used for four purposes, and in all cases are stored in the \s
> subdirectory and referenced from a main part with a type 1 line.
>
> 1 <colour> 0 0 0 x 0 0 0 y 0 0 0 z s\nnnnSnn
>
> * A part has many patterned versions
>
> Example: the minifig torso, see 973.dat and s\973s01.dat.
> * The plain (non-decorated) regions of the part are created as a subpart,
> which is referenced (with a type 1 line) by the main part file and each of the
> decorated part files. The subpart would be named by appending S01 to the main
> part file name. The part has a high degree of symmetry
>
> Example: some of the wheels, such as 2593.DAT.
> * As a way of reducing the size of the part files, the repeated region is
> created as a subpart and referenced several times by the main part file.
> Multiple subparts may be utilised if needed. Such subparts are typically
> numbered by appending Snn to the main part file name. Some elements are shared
> between several parts
>
> Example: the Wolfpack flag 2335P44.DAT and shield 3846P44.DAT .
> Such subparts are also numbered by uniquely modifying the patterned part
> number, but may be referenced from more than one base part file.
>
> *******************************
>
> ... the subparts for 004219b.dat should be numbered s\004219bsXX.dat.
>
> are you ready for headaches? I currently have a subpart at the PT which is
> numbered 4216816s.dat
> http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/s/4216816s.dat because
> otherwise it wouldn't not fit into a 20 years old nomenclatura. but there is
> more. 4216816s.dat is the subpart of 4216816a.dat Sticker System US-Flag Pattern
> Small http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/4216816a.dat the naming
> of the part respects the sticker standard while it reuses a subpart from
> 004159e.dat - Sticker System with United States Flag Pattern numbered
> s\004159e1.dat - ~Sticker System US-Flag Pattern - Star
> http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/s/004159e1.dat
>
> be aware! I do not blame the PT admin for this odd numbering. all this struggle
> comes from the limitation of the 8.3 nomenclature! the subpart numbering
> standard works fine with small numbers see: s\s1s01.dat - ~Thin Box for Square
> Flag Stickers but is inadequate for large ones.
>
> therefore I asks for a proper (logical?) naming standard for 10 and more
> subparts in a sticker in addition to this:
>
> "The part number for the sticker file is the SKU from the edge of the sticker
> sheet suffixed with a single letter. Each sticker from a single sheet should
> have a unique suffix. If the entire sheet is modelled in one part file then use
> the SKU with no suffix. If the SKU is unknown then the part number is "sXXX"
> where "XXX" is a number assigned by the Parts Tracker admin."
>
> or kicking the 8.3 nomenclature altogether (my preferred solution) in prospect
> of patterned parts with 6 or 7 digits: 123456p11.dat
>
> w.
Hi Willy,
Nice explanation about naming.
The issue of 8.3 nomenclature falls under the purvue of the
Standards Committee. Before they can remove that constraint,
they will have to work with the community of tool developers
to understand the impact to their code. I'm not on the
Standards Committee, but I'd guess the biggest issue might
be that non-8.3 compliant files will not work with James'
LDraw program, which is still the gold standard for what is
LDraw compatible.
Kevin
|
|
Message has 1 Reply:
 | | Re: Getting rif off the 8.3 nomenclature???
|
| (...) Hi Kevin, frankly I never understood how and why a program (I've never used BTW) can set a standard! I don't use Office progs from Redmond but I doubt that the file format for Word2007 has to be compatible with Word for DOS 5.5. Hang on! (...) (17 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
|
Message is in Reply To:
25 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
|
|
|
|
