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 / 4122
4121  |  4123
Subject: 
Re: MPD spec
Newsgroups: 
lugnet.cad.dev
Date: 
Wed, 8 Mar 2000 12:44:04 GMT
Reply-To: 
Rui.Martins@link.+stopspam+pt
Viewed: 
885 times
  
On Mon, 6 Mar 2000, Paul Gyugyi wrote:
In lugnet.cad.dev, Rui Manuel Silva Martins writes:
This is My proposition for changing the MPD format:
(how to build My proposition MPD)

I understand your proposal, but it has the bad side effect of
requiring a double-pass through all the files.

I'm sorry bu this is NOT true !
Also my suggestion to the MPD format only assumes an implicit (0 FILE
model.dat) at the begining of the file. so the processing is almost
exactly the same as before.

For example, if the first line of your file is:
1 1 0 0 0 1 0 0 0 1 0 0 0 1 foo.dat
and foo.dat is not found in the search path, the rendering
program does not know whether to print an error message or
do a complete pass through all the files to see if there
is a "0 FILE foo.dat" line later.

The current (the one beeing used now) MPD format also requires you to
search the rest of the MPD file for files, since the main model file is
defined as the first file defined in a (0 FILE filename) metacommand.

So as I said before, processing is almost exactly the same, just the error
checking in the begining is NOT required (to check that NO commands are
issued before the first (0 FILE filename) meta command).

Personally, if we were to change .MPD, I'd prefer a
"0 DEFINE foo.dat" and "0 DEFINE END" delimiters,
and require they be at the start of the file, with drawing
commands for the main part coming at the end. This would
make it easier to distribute parts libraries, do pre-caching
of files, and redefine parts.

That ideia about part libraries is interesting ! we could just use a
regular MPD, but with a different extension (.DLB ? for Dat LiBrary )
And we would have to find a way to inform the rendering/editing program to
used the specific (.DLB) library file.

You can do caching as you read the MPD file as it is today or with my
sugestion, it's easy.

the ideia of redefine parts, if I understood it correctly, can be
implemented easily, by search for a file in the MPD first, and only if not
found than search in the LDRAW dirs. This would be the way I would do the
search, at least for a MPD.

see ya.
Rui Martins



Message is in Reply To:
  Re: MPD spec  [DAT]
 
(...) I understand your proposal, but it has the bad side effect of requiring a double-pass through all the files. For example, if the first line of your file is: 1 1 0 0 0 1 0 0 0 1 0 0 0 1 foo.dat and foo.dat is not found in the search path, the (...) (25 years ago, 6-Mar-00, to lugnet.cad.dev)

65 Messages in This Thread:




















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

Custom Search

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