[ODE] File formats, was Re: .NET wrapper

[David Walker]

I too had been thinking about a file format to store this kind of
information. The way I was leaning was towards using the .NET serialization
features. That way ode objects could be included in a bigger structure
that could all be serialized in one go. I've used the .NET XML serialization
before and found it to be ok but I don't know how well it would suit. Also I
seem to remember it being fairly slow, I think because it uses reflection,
which is slow. It's just an idea at the moment but I was going to look at
adding it to my wrapper at some point.

David

----- Original Message -----
From: "Anselm Hook" <anselm@hook.org>
To: "Nate W" <coding@natew.com>
Cc: <ode@q12.org>
Sent: Tuesday, January 28, 2003 2:36 AM
Subject: Re: [ODE] File formats, was Re: .NET wrapper


>
> I googled that citation on the ODE list - hmmm.  XML *really* is a lot
> more stable.  I'm leery of anything that I have to use a special parser
> on.  For example what if I want to do an XSLT transformation on a dataset?
> Or what about doing RSS or RDF type feeds where say a website could use
> moveabletype to pluck out a 3d view of a users blog and then generate an
> ODE physics world from that...  by straying from XML one is left way out
> in the middle of nowhere...  (much as XML sucks).  No, I think your
> approach is better - it doesn't need more code all it needs is to be
> proclaimed as a standard...  entified by having its own page and being
> formally presented...  then the wars can begin.
>
>  - a