Subject:
|
Re: MPD spec
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Fri, 10 Mar 2000 15:43:02 GMT
|
Reply-To:
|
RUI.MARTINS@LINKsaynotospam.PT
|
Viewed:
|
1489 times
|
| |
|
|
> Steve:
>
> > I think part of the problem is that MPD files are currently being used
> > differently than they were originally intended. Rui's ideas would
> > benefit a lot of people trying to make use of MPD. But these changes
> > would defeat current uses of the format.
>
> Yes.
Also agree !
But, lets try to make everybody happy ! ;)
> I think that the right format for these alternative uses is
> gzipped tar files. There is Open Source code available for
> reading this format, and there is no need to go through a
> specification and implementation process.
I don't quite agree with that, because this new format does not need to be
just a way to gather a few DAT files, It can be a lot more, but without
forgetting that it should be kept simple.
So here are a few ideias (for a possibly new format):
Lets call it a "scene" file !
Where you could define, for example a city block, by refering several
different builds, but reusing some.
a "scene" can also be just a simple "model", like the ones we currently
represent in an MPD format
Not forgetting the great ideia of DAT libs, this format could support also
this, without an implied "model", just a bunch of DAT's (PARTS),
eventually a Lib with cenarios, a floor, a mountain, a lake, a bridge,
your space station or lunar soil background, etc....
The ideia here would be to be able to define a "scene", (later we can
discuss better terms), but to NOT require that every "background" or
"model" or DAT file referenced in the "scene" (scenario) be part of the
"scene" file (something like DAT parts or primitives)
Just make a flexible format, to allow for combinations of these ideias,
and eventually other that you guys come across.
Now to correctly define a format, (that makes everybody happy), we (i.e.
at least I) need to know what are the requirements and the restrictions.
- As requirements I would advance the above mentioned ideias.
- As restrictions, any that you guys can come up with, to allow the file
to be easily transfered by any means (NNTP- News, SMTP - Mail, etc..) and
or batch processed !
Not to clutter up this mail, and to let you guys shew on this ideias a
bit, I will make my concrete proposition, in another mail.
NOTE: Ideias are welcome, as always.
P.S.
If think about it, this can be done with regular DAT files, but the
flexibility isn't there, so this would be easy to implement as
meta commands. We just have to add some "context" to the DAT files.
See ya
Rui Martins
(Let's NOT make a big fuss of this, lets try to keep it simple and
concise)
|
|
Message is in Reply To:
 | | Re: MPD spec
|
| Steve: (...) Yes. I think that the right format for these alternative uses is gzipped tar files. There is Open Source code available for reading this format, and there is no need to go through a specification and implementation process. Play well, (...) (25 years ago, 10-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
|
|
|
|
