Subject:
|
Re: Straightening Up the MPF Format
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Fri, 2 Apr 2010 10:19:12 GMT
|
Viewed:
|
23419 times
|
| |
|
|
In lugnet.cad, Tore Eriksson wrote:
> Maybe it's time to straighten up the MPD standard. In
> http://www.ldraw.org/Article47.html it says:
> "So far, there are no clear scoping or namespace rules on MPD files. If you put
> a file named stud.dat in your MPD file, don't be surprised to see your stud.dat
> file appear on the top of every single brick in your scene."
>
> I think this problem should and can be solved. The only real problem is that MPD
> has been around for so many years without having been really standardized. The
> behaviour is a little bit random as it may vary from app to app.
>
> What if we make a recommendation that new software with MPD support optionally
> includes parent object's file name in its MPD-internal name? And if the software
> has an unpack function, user may choose to keep that safer name or to restore
> its original name. Of course the program should not freak out when confronted to
> an MPD file made by older software.
>
> For example:
> House1.ldr was first added to village.mpg
> House1.ldr has a reference to the submodel file door.ldr
> In village.ldr, door.ldr in internally named House1_ldr_door.ldr
> Then House2.ldr was added to village.mpd
> House2.ldr also has a reference to a submodel file named door.ldr, but different
> to the door used in House1.ldr.
> Now, with current MPD standards, the two models named door.ldr will cause a
> conflict within village.mpd. But with the approach I now suggest, the newly
> added door will be named House2_ldr_door.ldr and a naming conflict will be
> avoided.
>
> The downside with this would likely be very long object names if models are
> nested in say, five or six or more layers of sub-models.
>
> This is just my first thoughts, and I'm kind of a newbie when it comes to MPD.
> Hopefully, someone can improve this first, crude idea so we finally may present
> something for the standards committee to decide on.
>
> Any thoughts?
>
> /Tore
Please see here for the search strategie for referenced files:
http://news.lugnet.com/cad/dev/?n=5522
At present your problem can only be solved by hand to give all files in the MPD
file a unique name.
I do not know any app so far that will assist you in that.
So far I do not think that there has to be an addition to the specs, maybe only
information about the search strategie for references that is used.
Once I have finished my new MPDCenter it will do that for you. Maybe the old
version still works, but I have no sourcecode to improve on that version instead
I am working on a new version under .NET (hopefully workable also under MONO).
cu
mikeheide
|
|
Message is in Reply To:
 | | Straightening Up the MPF Format
|
| Maybe it's time to straighten up the MPD standard. In (URL) it says: "So far, there are no clear scoping or namespace rules on MPD files. If you put a file named stud.dat in your MPD file, don't be surprised to see your stud.dat file appear on the (...) (15 years ago, 2-Apr-10, to lugnet.cad)
|
19 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
