[ODE] XODE trimesh structure - please vote

[Roel van Dijk]

On Tuesday 16 March 2004 18:30, Jon Watte wrote:
> > And because it is only meant as an interchange format I think the
> > advantages of XPath and XSLT outweigh the disadvantages of slower parsing
> > and larger filesize.
>
> I think this is the real question. Is this a format that can conceivably be
> used for real storage, or is it specifically designed to be as slow as
> possible to ease obscure interchange cases? If so, what, specifically, are
> those concrete interchange cases?
Good point. I thought the x,y,z attributes would come in handy when you would 
want to do something like swapping all y and z values. But I think that can 
also be achieved fairly easily by modifying the reader.

If I would use XODE in my app then I would prefer to store it as text or as 
gzipped text for permanent storage. Only when transfering things over a 
network would I consider a binary format. But I am quite inexperienced when 
it comes to things like multiplayer games :-)

I can't really choose between option #1 or #2. But I'm against #3 because it 
will only make the task of writing a reader more complex.