Subject:
|
Re: IMPORTANT - [ldraw.org] Official Model Repository
|
Newsgroups:
|
lugnet.cad.dev.org.ldraw
|
Date:
|
Sat, 12 Jun 1999 19:05:10 GMT
|
Viewed:
|
1139 times
|
| |
|
|
We MUST keep it in 8+3 format because SOME PEOPLE still do use
LEdit, and if you don't have the files in 8+3 format you can't
use the files.
I think that the way something like the Mos Espa set should be
done is
like this(I don't have the set so this is just an example)
S7171-99.dat The complete set
S7171a.dat Anakin's Podracer
S7171a1.dat A's P cockpit section
S7171a2.dat A's P engine front
S7171a3.dat A's P engine back
S7171a4.dat A's P Pit Droid
S7171a5.dat A's P Pit
etc. for the rest
I personally think that a submodel like those for the engine,
should be inlined
because they are part of the engine and are stationary.
Does this make any sense whatsoever??
Ryan
*********** REPLY SEPARATOR ***********
On 6/12/99, at 2:34 PM, lehman@javanet.com wrote:
> In lugnet.cad.dev.org.ldraw, braml@juno.com (Bram Lambrecht) • writes:
> > [...]
> > sXXXX-YY.dat
> > display file, XXXX is the set number, YY is the year, shows • all models
> > and alternate models, possibly with 0 CLEAR inbetween.
> >
> > sXXXX-a.dat main set of instructions, first model.
> > sXXXX-aa.dat main instructions, first model, first component • (submodel)
> > sXXXX-ab.dat main instructions, first model, second component • (submodel)
> > etc.
> > sXXXX-b.dat main instructions, second model.
> > sXXXX-ba.dat main instructions, second model, first component
> > etc.
> >
> > sXXXXaa.dat first alt. instructions, first model.
> > sXXXXaaa.dat first alt. instructions, first model, first • component
> > sXXXXaab.dat first alt. instr, first model, second component.
> > etc.
>
> Bram,
> I think that's definitely on the right track! (At least with • the double-
> and triple-letter combinations.)
>
> A great example of double-lettering is the 7171 Mos Espa • Podrace™ set --
> each of the three submodels of 7171 has itself three submodels: • (a) a
> podracer, (b) a pit droid, and (c) a little service stand • thingie. The pit
> droid might even arguably be a submodel of the service stand, • or the service
> stand and the pit droid together might be a submodel of the • virtual-pair.
>
> Anyway, your proposal above obviously breaks the 8.3 rule -- • which I think
> is a Good Thing if it can be made to work. The legacy of 8.3 • filenames
> would be a terrible, terrible thing to carry into the next • millennium, IMHO.
>
> BTW, the year could even be written as a four-digit number if • 8.3 wasn't an
> issue.
>
>
> > I hope that's clear enough :) This system would also allow • official
> > alternate models without instructions (ie those on the back • of the box)
> > to be included when someone figures out how to build them.
>
> Regardless of all of the mixed opinions here on this subject • (of the
> dataifcation of alternate models without instructions) -- I • think it would
> be a very good thing at least to _plan_for_it_ in the • namespace.
>
> All of the naysayers should bear this in mind: You don't • necessarily need
> building instructions for all alternate models! Yes, with most • (maybe 97%),
> you *do* really need them to get it correct, but there are • hundreds of very
> small sets where the alternate models are 100.000% clear on the • box.
>
> Take some of the Christmas holiday polybags, for example. • There's no reason
> to preclude their alternate models just because official • building
> instructions aren't present. In fact, some *main* models are • so simple that
> they don't even come with building instructions! :)
>
>
> > This could lead to giant MPD files for every set, though, • making me
> > wonder if ZIP wouldn't be a better format. (Maybe both?) • With ZIP, you
> > could also create a directory for every model's submodels. • Then you
> > wouldn't be limited to only 3 characters for naming all the • components.
> > eg:
> >
> > sXXXX-YY.dat same as above, but references to • components
> > changed to use the directory
> > sXXXX-YY\main-a.dat same as sXXXX-a.dat above
> > sXXXX-YY\main-aa.dat same as sXXXX-aa.dat above
> > sXXXX-YY\alt1-a.dat same as sXXXXaa.dat above
> > sXXXX-YY\alt1-aa.dat same as sXXXXaaa.dat above
> > sXXXX-YY\alt2-a.dat same as sXXXXba.dat would be above
>
> OOOH OOOH -- Subdirectories! -- GOOD IDEA -- Good path to • explore/brainstorm
> down...
>
> Could it work??? How might it work in practice?
>
> Does LDLITE handle embedded /'s in "0 FILE" invocations? How • about type-1
> lines in DAT files? Can you have something like this?--
>
> 1 <affine transformation> foo/bar/glort.dat
>
> Say, BTW, instead of an "S" prefix on the filenames, couldn't • there be a
> SETS directory beneath the C:\LDRAW directory? There is • already a MODELS
> and a PARTS subdirectory. It could maybe even go beneath the • MODELS
> directory...
>
> Then (this is maybe getting out on a limb) you could have:
>
> C:\LDRAW\MODELS\SETS\1974-90A\MAIN.DAT => Flyercracker • U.S.A.
> C:\LDRAW\MODELS\SETS\1974-90B\MAIN.DAT => Smuggler's • Hayride
> C:\LDRAW\MODELS\SETS\1974-90C\MAIN.DAT => Star Quest
> C:\LDRAW\MODELS\SETS\7171-99A\MAIN.DAT => Mos Espa • Podrace™ - Anakin
> C:\LDRAW\MODELS\SETS\7171-99A\MAIN-A.DAT => podracer
> C:\LDRAW\MODELS\SETS\7171-99A\MAIN-BA.DAT => service • thingie
> C:\LDRAW\MODELS\SETS\7171-99A\MAIN-BB.DAT => pit droid
> C:\LDRAW\MODELS\SETS\7171-99A\MAIN.DAT => Mos Espa • Podrace™ - Gasgano
> C:\LDRAW\MODELS\SETS\7171-99A\MAIN-A.DAT => podracer
> C:\LDRAW\MODELS\SETS\7171-99A\MAIN-BA.DAT => service • thingie
> C:\LDRAW\MODELS\SETS\7171-99A\MAIN-BB.DAT => pit droid
> C:\LDRAW\MODELS\SETS\7171-99A\MAIN.DAT => Mos Espa • Podrace™ - Sebulba
> C:\LDRAW\MODELS\SETS\7171-99A\MAIN-A.DAT => podracer
> C:\LDRAW\MODELS\SETS\7171-99A\MAIN-BA.DAT => service • thingie
> C:\LDRAW\MODELS\SETS\7171-99A\MAIN-BB.DAT => pit droid
> ^^^^^^^^
> NNNN-YYI
>
> (Sorry for all the uppercase and backslash garbage (DOS legacy • stuff), but I
> wanted to be 100% clear in getting the idea across.)
>
> If there's going to be potentially multiple files per LEGO set, • then it
> seems like a bad idea *not* to use subdirectories -- if it's • possible to use
> them...?
>
> --Todd
|
|
Message has 2 Replies:
Message is in Reply To:
94 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
|
|
|
|
