Talk:Proposals/Unified Mesh Format

From UFO:AI
< Talk:Proposals
Revision as of 04:32, 30 November 2012 by Kildor (talk | contribs) (Naming: TextureCoordinate is way too long, […] What is better?: new section)

I realize this is far beyond my expertise, but is there a reason that we're not looking to implement an existing, widely used and widely supported format? Are we talking here about creating our own format? Does that mean maintaining our own tools, import/export plugins, etc? Or am I missing something? --H-hour 02:37, 30 November 2012 (SAST)

In fact, this is about the internal representation of mesh data, not the storage (file) format (which I think Sandro would also like to unify, but that's a different matter).
--DarkRain 03:57, 30 November 2012 (SAST)

Naming: TextureCoordinate is way too long, […] What is better?

As far as I know, the compiled code has no names of variables. When you write the code you can use autocompleting and other tips, so readability and clearing of code is better than economy of symbols.